From: "John M. Aldrich" Newsgroups: comp.os.msdos.djgpp Subject: Re: rhide/call trace back - small question Date: Sat, 22 Feb 1997 02:04:27 -0800 Organization: Two pounds of chaos and a pinch of salt Lines: 31 Message-ID: <330EC4AB.77E1@cs.com> References: <330D08FC DOT 4034 AT mbnet DOT mb DOT ca> Reply-To: fighteer AT cs DOT com NNTP-Posting-Host: ppp107.cs.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Alex Demko wrote: > > I noticed that rhide can show you a call stack when a program bombs > under it. > > Now lets say a person sent me a screen dump (see bottom of this message) > of that GPF screen that occured in a program I wrote. Can I somehow > recreate a call stack from that info to aid me in finding the bug? If you and the person who experienced the crash both have _exactly_ the same build of the program, then all you need to do is the following: - put the complete core dump into a file - make sure your version is compiled with debugging info ('-g') - type "symify -i myprog.exe" This will output a readable stack trace. BTW, you seem to be making the common mistake of thinking of RHIDE as a compiler. It isn't - it's just an editor that is capable of invoking the compiler tools. The core dump you see is generated by the _program_; RHIDE reads it and uses its own 'symify' to generate a readable stack trace. It may even use DJGPP's symify; I'm not sure. -- --------------------------------------------------------------------- | John M. Aldrich, aka Fighteer I | fighteer AT cs DOT com | | Call me for your free AOL disk! | http://www.cs.com/fighteer | | Chain letters, work-at-home schemes, free long distance, etc., | | are ILLEGAL! Keep the Internet litter-free... don't SPAM. | ---------------------------------------------------------------------