|
|
Purify or other malloc checkers. |
On Jan 19, 1996, Larry Phelps said:
I know of two such products for SCO Unix these:
Insure++:
Parasoft Corporation
2031 South Myrtle Avenue
Monrovia, CA 91016
Phone: (818) 305-0041
Fax: (818) 305-9048
Email: insure@parasoft.com
HTTP: http://www.parasoft.com
Sentinel:
AIB Software Corporation
1145 Herndon Parkway
Herndon, Virginia 22070
Phone: (703) 787-7700
Fax: (703) 787-7720
Email: info@aib.com
HTTP: http://www.aib.comrobertlipe@usa.net | |
| checkergcc exists for linux. Could probably be ported to SCO systems.
robertlipe@usa.net | |
| For C++, the UnixWare 2.x and UDK Standard Components has a memory checking tool called 'fs'. It's not as powerful or transparent as commercial tools such as Purify, but it's better than nothing. | |
| On UnixWare 7 and on UDK, the standard malloc library has instrumentation
that can be turned on at runtime. If you export MALLOC_CHECKS, you can
control the tests that are performed on the heap. UnixWare 7.1.0 has even more instrumentation and can deliver a SIGSEGV (conveniently trapping you into a debugger) at the bus cycle that delivers the bounds exception. robertlipe@usa.net | |
| Electric Fence from Bruce Parens works just fine on OpenServer. I don't
really know that it offers anything above the MALLOC_CHECKS tests in the system
libraries.
robertlipe@usa.net | |
| dmalloc (www.dmalloc.com) works fine with OSR5.
john@kuwait.net | |
| Beginning with UnixWare 7.1.3 there is the "memtool" tool, which does a lot of the memory error detection work that commercial tools like Purify do.
See http://uw713doc.sco.com/en/man/html.1/memtool.1.html or the memtool(1) man page on your system.
jls@sco.com | |
| [Append to This Answer] |
| Previous: |
|
| Next: |
|
| ||||||||