DOCSLIB.ORG

Purify User's Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Purify User's Guide Purify User’s Guide Version 4.0 [email protected] http://www.pure.com IMPORTANT NOTICE DISCLAIMER OF WARRANTY Pure Software Inc. makes no representations or warranties, either express or implied, by or with respect to anything in this guide, and shall not be liable for any implied warranties of merchantability or fitness for a particular purpose or for any indirect, special or consequential damages. COPYRIGHT NOTICE Purify, copyright 1992-1996 Pure Software Inc. All rights reserved. Purify, PureCoverage, and Quantify are covered by one or more of U.S. Patent Nos. 5,193,180, 5,335,344, and 5,535,329. Purify is licensed under Sun Microsystems Inc.'s U.S. Pat. No. 5,404,499. Other U.S. and foreign patents pending. No part of this publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, photocopying, recording or otherwise, without prior written consent of Pure Software Inc. No patent liability is assumed with respect to the use of the information contained herein. While every precaution has been taken in the preparation of this book, Pure Software Inc. assumes no responsibility for errors or omissions. This publication and features described herein are subject to change without notice. The program and information contained herein are licensed only pursuant to a license agreement that contains use, reverse engineering, disclosure and other restrictions; accordingly, it is “Unpublished — rights reserved under the copyright laws of the United States” for purposes of the FARs. RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure by the Government is subject to the restrictions as set forth in subparagraph (c) (1) (a) of the Rights in Technical Data and Computer Software clause of the DFARs 252.227-7013 and FAR 52.227-19(c) and any successor rules or regulations. TRADEMARKS Pure Software, PureCoverage, Quantify, PureLink, and Purify are U. S. registered trademarks of Pure Software Inc. PureVision, PureDDTS, WebTracker, WebTrackerLite, and the Pure Software logo are U. S. trademarks of Pure Software Inc. All other products or services mentioned in this guide are covered by the trademarks, service marks, or product names as designated by the companies who market those products. Printed in the U.S.A. on recycled paper. PURIFY USER’S GUIDE Contents Welcome to Purify Getting started . .xi Mastering the basics . .xi Learning to use special features . .xi Using the reference chapters . xii Using online Help . xii Conventions used in this guide . xiii Displaying the release notes . xiii Installing Purify . xiii Contacting technical support . xiv 1 Introducing Purify When to use Purify . 1-2 Starting to use Purify . 1-3 Getting the most out of Purify . 1-5 Customizing Purify . 1-5 Using your debugger with Purify . 1-5 Calling Purify’s API functions . 1-6 Integrating Purify into makefiles and scripts . 1-6 Using Purify with other Pure Software products . 1-7 Using Purify with PureCoverage . 1-7 Using PureLink with Purify and PureCoverage . 1-8 Using Purify with PureDDTS . 1-8 Using Purify with PureTestExpert . 1-8 Checking for memory errors . 1-9 Memory access errors . 1-9 Accessing through dangling pointers . 1-9 iii Uninitialized memory reads . 1-10 Memory allocation errors . 1-10 Memory leaks . 1-11 Errors in third-party code and libraries . 1-11 2 Finding Errors in Hello World Before you start . 2-2 Building a Purify’d program . 2-3 Compiling and linking in separate stages . 2-3 Running a Purify’d program . 2-4 Using the Purify Viewer . 2-5 Analyzing an ABR message . 2-6 Using line numbers and source filenames . 2-7 Finding the exact location of the error . 2-8 Correcting the ABR error . 2-9 Looking at the file descriptors message . 2-10 Understanding the memory leaked summary . 2-11 Looking at the MLK error . 2-12 Looking at the exit status summary . 2-14 Rerunning a Purify’d program . 2-15 3 Memory Access Errors How Purify finds memory access errors . 3-2 How Purify checks statically allocated memory . 3-4 Notes and limitations . 3-5 Building the testHash example program . 3-6 Running the testHash program without Purify . 3-7 Running the Purify’d testHash program . 3-8 Debugging the testHash program . 3-9 Debugging with dbx . 3-9 Debugging with xdb . 3-10 Reading uninitialized memory . 3-11 A UMR example . 3-11 iv Finding the cause of the UMR error . 3-13 Correcting the UMR error . 3-13 Reading and writing beyond the bounds of an array . 3-14 An ABW example . 3-14 Finding the cause of the ABW error . 3-15 Correcting the ABW error . 3-16 An ABR example . 3-16 Reading or writing freed memory . 3-17 An FMR example . 3-18 Finding the cause of the FMR error . 3-19 Correcting the FMR error . 3-20 Freeing unallocated or non-heap memory . 3-21 An FNH example . 3-21 Finding the cause of the FNH error . 3-22 Correcting the FNH error . 3-23 4 Memory Leaks How Purify reports memory leaks . 4-1 Notes and limitations . 4-3 Finding the memory leaks in testHash . 4-4 Finding the source of memory leaks . 4-6 Using your debugger to set breakpoints . 4-7 Running purify_new_leaks . 4-8 Correcting the error . 4-10 Using the new leaks button . 4-10 Disabling memory leaked messages . 4-11 5 Analyzing File Descriptors File descriptors in use messages . 5-1 File descriptor leak example . 5-3 Analyzing FIU messages . 5-4 Disabling FIU messages . 5-4 Notes and limitations . 5-4 v 6 Customizing Purify Controlling Purify output . 6-2 Saving Purify output as ASCII text . 6-2 Saving Purify output to a view file . 6-3 Prestarting the Viewer . 6-5 Mailing Purify output to developers . 6-6 Using the -mail-to-user-option . 6-6 Protecting your run-time option settings . 6-6 Annotating Purify’s output . 6-7 Customizing Purify messages . 6-9 Controlling the content and appearance of messages . 6-9 Controlling message batching . 6-9 Customizing the thread summary message . 6-10 Enabling JIT debugging . 6-11 Reporting Purify status at exit . 6-13 Running shell scripts at exit . 6-14 Customizing the Purify Viewer . 6-15 Customizing Purify scripts . 6-16 Customizing the program controls . 6-17 Managing cached object files . 6-19 Deleting cached object files . ..
Load more

Recommended publications
  • Using Restricted Transactional Memory to Build a Scalable In-Memory Database
    Using Restricted Transactional Memory to Build a Scalable In-Memory Database Zhaoguo Wang†, Hao Qian‡, Jinyang Li§, Haibo Chen‡ † School of Computer Science, Fudan University ‡ Institute of Parallel and Distributed Systems, Shanghai Jiao Tong University § Department of Computer Science, New York University Abstract However, the correctness of the resulting code is complex to reason about and relies on the processor’s (increasingly The recent availability of Intel Haswell processors marks the complex) memory model. transition of hardware transactional memory from research Recently, Intel has shipped its 4th-generation Haswell toys to mainstream reality. DBX is an in-memory database processor with support for Hardware Transactional Mem- that uses Intel’s restricted transactional memory (RTM) to ory [16]. This opens up a third possibility to scaling multi- achieve high performance and good scalability across multi- core software. Instead of relying on fine-grained locking core machines. The main limitation (and also key to practi- and atomic operations, one can synchronize using hardware cality) of RTM is its constrained working set size: an RTM transactions, which offer a programming model that is ar- region that reads or writes too much data will always be guably even more straightforward than mutual exclusion. aborted. The design of DBX addresses this challenge in sev- The promise is that the resulting implementation is much eral ways. First, DBX builds a database transaction layer on simpler and easier-to-understand while still retaining the top of an underlying shared-memory store. The two layers performance benefits of fine-grained locking. use separate RTM regions to synchronize shared memory Does hardware transactional memory actually deliver its access.
    [Show full text]
  • Using the GNU Compiler Collection (GCC)
    Using the GNU Compiler Collection (GCC) Using the GNU Compiler Collection by Richard M. Stallman and the GCC Developer Community Last updated 23 May 2004 for GCC 3.4.6 For GCC Version 3.4.6 Published by: GNU Press Website: www.gnupress.org a division of the General: [email protected] Free Software Foundation Orders: [email protected] 59 Temple Place Suite 330 Tel 617-542-5942 Boston, MA 02111-1307 USA Fax 617-542-2652 Last printed October 2003 for GCC 3.3.1. Printed copies are available for $45 each. Copyright c 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with the Invariant Sections being \GNU General Public License" and \Funding Free Software", the Front-Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the section entitled \GNU Free Documentation License". (a) The FSF's Front-Cover Text is: A GNU Manual (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. i Short Contents Introduction ...................................... 1 1 Programming Languages Supported by GCC ............ 3 2 Language Standards Supported by GCC ............... 5 3 GCC Command Options .........................
    [Show full text]
  • Oracle Solaris Studio 12.3 Debugging a Program With
    Oracle® Solaris Studio 12.3: Debugging a ProgramWith dbx Part No: E21993 December 2011 Copyright © 1992, 2011, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms setforth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
    [Show full text]
  • Debugging a Program with Dbx
    Debugging a Program With dbx Sun™ Studio 11 Sun Microsystems, Inc. www.sun.com Part No 819-3683-10 November 2005, Revision A Submit comments about this document at: http://www.sun.com/hwdocs/feedback Copyright © 2005 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements. Use is subject to license terms. This distribution may include materials developed by third parties. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, Java, and JavaHelp are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon architecture developed by Sun Microsystems, Inc. This product is covered and controlled by U.S. Export Control laws and may be subject to the export or import laws in other countries. Nuclear, missile, chemical biological weapons or nuclear maritime end uses or end users, whether direct or indirect, are strictly prohibited. Export or reexport to countries subject to U.S. embargo or to entities identified on U.S. export exclusion lists, including, but not limited to, the denied persons and specially designated nationals lists is strictly prohibited.
    [Show full text]
  • A Short User Manual for Dbx
    A Short User Manual for dbx \dbx" is the name of the debugger that is available for use on many Unix systems. This document is intended to list the most common dbx commands and briefly explain how to use them. It is not a complete description of dbx but should be a sufficient reference to get started. For a more detailed description or to find out about other commands and options, execute the command % man dbx or from within dbx use the 'help' command (recommended). Subjects covered below: let (dbx) be the prompt while in dbx mode: a) Compiling your code for use with the debugger [ cc with -g flag] b) Starting the debugger [ \%dbx executable ] c) Getting help while using the debugger [ (dbx) help ] d) Running your program in the debugger [ (dbx) run ] e) Setting breakpoints in the program [ (dbx) stop ] f) Listing the breakpoints that are set [ (dbx) status ] g) Removing a breakpoint [ (dbx) delete ] h) Stepping through the program [ (dbx) step, (dbx) next ] i) Jumping ahead to the next breakpoint [ (dbx) cont ] j) Examining the values of variables [ (dbx) print ] k) Listing a portion of the source code [ (dbx) list ] l) Leaving the debugger [ (dbx) quit ] To use dbx to debug your C programs you need to follows the procedure: 1. Compiling your code for use with the debugger: You must use the -g flag when compiling your code. For example: % cc -g myfile.c will create an a.out executable suitable for dbx. 2. Starting the debugger: Give the 'dbx' command along with the name of the exe- cutable you wish to examine.
    [Show full text]
  • Debugging a Program with Dbx
    Debugging a Program With dbx A Sun Microsystems, Inc. Business 901 San Antonio Road Palo Alto, , CA 94303-4900 Part No: 805-4948 Revision A, February 1999 USA 650 960-1300 fax 650 969-9131 Debugging a Program With dbx Part No: 805-4948 Revision A, February 1999 Copyright 1999 Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, California 94303-4900 U.S.A. All rights reserved. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Portions of this product may be derived from the UNIX® system, licensed from Novell, Inc., and from the Berkeley 4.3 BSD system, licensed from the University of California. UNIX is a registered trademark in the United States and in other countries and is exclusively licensed by X/Open Company Ltd. Third-party software, including font technology in this product, is protected by copyright and licensed from Sun’s suppliers. RESTRICTED RIGHTS: Use, duplication, or disclosure by the U.S. Government is subject to restrictions of FAR 52.227-14(g)(2)(6/87) and FAR 52.227-19(6/87), or DFAR 252.227-7015(b)(6/95) and DFAR 227.7202-3(a). Sun, Sun Microsystems, the Sun logo, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and in other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc.
    [Show full text]
  • Using and Porting the GNU Compiler Collection
    Using and Porting the GNU Compiler Collection Richard M. Stallman Last updated 14 June 2001 for gcc-3.0 Copyright c 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001 Free Software Foundation, Inc. For GCC Version 3.0 Published by the Free Software Foundation 59 Temple Place - Suite 330 Boston, MA 02111-1307, USA Last printed April, 1998. Printed copies are available for $50 each. ISBN 1-882114-37-X Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with the Invariant Sections being “GNU General Public License”, the Front-Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the section entitled “GNU Free Documentation License”. (a) The FSF’s Front-Cover Text is: A GNU Manual (b) The FSF’s Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. Short Contents Introduction......................................... 1 1 Compile C, C++, Objective C, Fortran, Java ............... 3 2 Language Standards Supported by GCC .................. 5 3 GCC Command Options ............................. 7 4 Installing GNU CC ............................... 111 5 Extensions to the C Language Family .................. 121 6 Extensions to the C++ Language ...................... 165 7 GNU Objective-C runtime features .................... 175 8 gcov: a Test Coverage Program ...................... 181 9 Known Causes of Trouble with GCC ................... 187 10 Reporting Bugs.................................
    [Show full text]
  • Using the GNU Compiler Collection
    Using the GNU Compiler Collection Richard M. Stallman Last updated 20 April 2002 for GCC 3.2.3 Copyright c 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002 Free Software Foundation, Inc. For GCC Version 3.2.3 Published by the Free Software Foundation 59 Temple Place—Suite 330 Boston, MA 02111-1307, USA Last printed April, 1998. Printed copies are available for $50 each. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with the Invariant Sections being “GNU General Public License”, the Front-Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the section entitled “GNU Free Documentation License”. (a) The FSF’s Front-Cover Text is: A GNU Manual (b) The FSF’s Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. i Short Contents Introduction ...................................... 1 1 Compile C, C++, Objective-C, Ada, Fortran, or Java ....... 3 2 Language Standards Supported by GCC ............... 5 3 GCC Command Options .......................... 7 4 C Implementation-defined behavior ................. 153 5 Extensions to the C Language Family ................ 157 6 Extensions to the C++ Language ................... 255 7 GNU Objective-C runtime features.................. 267 8 Binary Compatibility ........................... 273 9 gcov—a Test Coverage Program ................... 277 10 Known Causes of Trouble with GCC ...............
    [Show full text]
  • Debugging a Program with Dbx
    Debugging a Program With dbx Forte Developer 7 Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. 650-960-1300 Part No 816-2453-10 May 2002, Revision A Send comments about this document to: [email protected] Copyright © 2002 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries. This document and the product to which it pertains are distributed under licenses restricting their use, copying, distribution, and decompilation. No part of the product or of this document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, Forte, Java, Solaris, iPlanet, NetBeans, and docs.sun.com are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc.
    [Show full text]
  • Oracle® Solaris Studio 12.4: Dbxtool Tutorial 2 > Display Var Will Display 'Var' > Stop in X > Run Running
    ® Oracle Solaris Studio 12.4: dbxtool Tutorial October 2014 Part No: E37084 ■ “Introduction” on page 2 ■ “Example Program” on page 2 ■ “Configuring dbxtool” on page 3 ■ “Diagnosing a Core Dump” on page 9 ■ “Using Breakpoints and Stepping” on page 13 ■ “Using Advanced Breakpoint Techniques” on page 22 ■ “Using Breakpoint Scripts to Patch Your Code” on page 39 Introduction This tutorial uses a “buggy” example program to demonstrate how to use dbxtool, the stand-alone graphical user interface (GUI) for the dbx debugger, effectively. It starts with the basics and then moves on to more advanced features. Example Program This tutorial uses a simplified and somewhat artificial simulation of the dbx debugger. The source code for this C++ program is available in the sample applications zip file on the Oracle Solaris Studio 12.4 downloads web page at http://www.oracle.com/technetwork/server-storage/solarisstudio/ downloads/index.html. After accepting the license and downloading, you can extract the zip file in a directory of your choice. 1. If you have not already done so, download the sample applications zip file, and unpack the file in a location of your choice. The debug_tutorial application is located in the Debugger subdirectory of the SolarisStudioSampleApplications directory. 2. Build the program. $ make CC -g -c main.cc CC -g -c interp.cc CC -g -c cmd.cc CC -g -c debugger.cc CC -g -c cmds.cc CC -g main.o interp.o cmd.o debugger.o cmds.o -o a.out The program is made up of the following modules: cmd.h cmd.cc Class Cmd, a base for implementing debugger commands interp.h interp.cc Class Interp, a simple command interpreter debugger.h debugger.cc Class Debugger, mimics the main semantics of a debugger cmds.h cmds.cc Implementations of various debugging commands main.h main.cc The main() function and error handling.
    [Show full text]
  • Dbx Reference Manual
    dbx Reference Manual IRIS-4D Series SiliconGraphics Computer Systems Document number" 007-0906-030 dbx Reference Manual Version 3.0 Document Number 007-0906-030 12/90 Technical Publications: Wendy Ferguson Beth Fryer Claudia Lohnes Robert Reimann Eng ineering: David Anderson Greg Boyd Jeff Doughty Jim Terhorst © Copyright 1990, Silicon Graphics, Inc. - All rights reserved This document contains proprietary information of Silicon Graphics, Inc. The contents of this document may not be disclosed to third ( parties, copied or duplicated in any form, in whole or in part, without the prior written permission of Silicon Graphics, Inc. Restricted Rights Legend Use, duplication or disclosure of the technical data contained in this document by the Government is subject to restrictions as set forth in subdivision (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 52.227-7013, and/or in similar or successor clauses in the FAR, or the DOD or NASA FAR Supplement. Unpublished rights reserved under the Copyright Laws of the United States. Contractor/manufacturer is Silicon Graphics Inc., 2011 N. Shoreline Blvd., Mountain View, CA 94039-7311. dbx Reference Manual Version 3.0 Document Number 007-0906-030 ( Silicon Graphics, Inc. Mountain View, California IRIX and WorkSpace are trademarks and IRIS is a registered trademark of Silicon Graphics, Inc. Contents 1. Introduction • • • • • 1-1 1.1 Using This Manual 1-1 1.2 Conventions • • 1-3 1.3 Relevant Documentation 1-4 2. Getting Started . • • • • 2-1 2.1 Debugging a Simple Program 2-1 2.2 Source-Level Debuggers 2-4 2.3 Activation Levels.
    [Show full text]
  • Programming on Silicon Graphics® Systems: an Overview
    Programming on Silicon Graphics® Systems: An Overview Document Number 007-2476-003 CONTRIBUTORS Written by Eleanor Bassler Edited by C. Kleinfeld Photography by Nancy Cam Production by Heather Hermstad St. Peter’s Basilica image courtesy of ENEL SpA and InfoByte SpA. Disk Thrower image courtesy of Xavier Berenguer, Animatica. © 1998, Silicon Graphics, Inc.— All Rights Reserved The contents of this document may not be copied or duplicated in any form, in whole or in part, without the prior written permission of Silicon Graphics, Inc. RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure of the technical data contained in this document by the Government is subject to restrictions as set forth in subdivision (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 52.227-7013 and/or in similar or successor clauses in the FAR, or in the DOD or NASA FAR Supplement. Unpublished rights reserved under the Copyright Laws of the United States. Contractor/manufacturer is Silicon Graphics, Inc., 2011 N. Shoreline Blvd., Mountain View, CA 94043-1389. Silicon Graphics, the Silicon Graphics logo, and IRIX are registered trademarks, and IRIS Graphics Library, IRIS IM, IRIS InSight, IconSmith, OpenGL, IRIS ViewKit, POWER Fortran Accelerator, IRIS Performer, Indigo Video, Indy Video, Galileo Video, Indigo2 Video, Sirius Video, ImageVision Library, CASEVision, Impressario, Indigo Magic, Open Inventor, POWER Series, and RealityEngine are trademarks, of Silicon Graphics, Inc. OSF/Motif is a trademark of Open Software Foundation. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd. X Window System is a trademark of the Massachusetts Institute of Technology.
    [Show full text]