Article View: comp.sys.next.programmer
Article #144Re: side effects of DPSTraceContext() ?
From: Josh Doenias
Date: Wed, 04 Nov 1992 23:00
Date: Wed, 04 Nov 1992 23:00
25 lines
1329 bytes
1329 bytes
In article <BRUECK.92Nov2171304@inmsol.inm.uni-sb.de> brueck@inm.uni-sb.de (Stefan Brueck) writes: > > which are the side effects of the DPSTraceContext() function? > >the answer could help me to solve a problem found in a programming session: .. This sounds to me like a classic memory smasher. You may be overwriting a pointer and stomping on memory somewhere. This could cause the crash you are seeing. Some change to the way the program runs (eg. compiling with debugging, calling some new function like DPSTraceContext()) may change the way things are laid out in memory in such a way that you no longer get a crasher (although you may still be writing into bad areas of memory). These are usually the hardest types of bugs to find in a program. gdb and MallocDebug are your friends in this case. Good luck in finding it! -- josh ##No disclaimer. If you want to hold my employer responsible for something I said, that's okay by me.
Technical Details
Message-ID:
<5746@rosie.NeXT.COM>Path:
arc1-ca.pugleaf.net!sparky!uunet!rosie!next.comReferences:
<BRUECK.92Nov2171304@inmsol.inm.uni-sb.de>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!rosie!next.com From: jdoenias@next.com (Josh Doenias) Newsgroups: comp.sys.next.programmer Subject: Re: side effects of DPSTraceContext() ? Message-ID: <5746@rosie.NeXT.COM> Date: 4 Nov 92 23:00:09 GMT References: <BRUECK.92Nov2171304@inmsol.inm.uni-sb.de> Sender: news@NeXT.COM Distribution: comp Lines: 25