Title: | ATOM Tool Development System |
Moderator: | CALDEC::SCHMIDT |
Created: | Tue Sep 07 1993 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 309 |
Total number of notes: | 979 |
May I suggest that atom provide a cut down version of 'third' which only performs memory allocation/deallocation analysis would be an advantage. Many applications are becomming bigger and bigger, and thus more and more time consuming to analys with the full 'third'. In my case the application takes more than an hour to startup when instrumented. The full 'third' would still be available when needed, but a smaller faster check just for memory alloc/dealloc would encourage more use of these tools. Peter.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
300.1 | Use uninit_heap and uninit_stack options? | SMURF::JPW | John P Williams, DUDE, USG, 381-2079 | Mon Apr 28 1997 10:09 | 15 |
Hi, I'm not sure if this is what you're looking for, but if you create a file called ".third" and write the following lines into it before running atom, it will omit the "uninitialized memory" checks, leaving only the alloc/dealloc checks: uninit_heap no uninit_stack no See the third(5) man-page for more info. If you're looking for something else, or if this does not save any appreciable amount of time during instrumentation, feel free to enter a qar in the osf_qar database on gorge:: (or another reply or email). |