From:	Alex Demko <ademko AT mbnet DOT mb DOT ca>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: rhide/call trace back - small question
Date:	Sat, 22 Feb 1997 17:29:02 -0600
Organization:	Chaos Software
Lines:	31
Message-ID:	<330F813E.77E1@mbnet.mb.ca>
References:	<330D08FC DOT 4034 AT mbnet DOT mb DOT ca> <330EC4AB DOT 77E1 AT cs DOT com>
NNTP-Posting-Host:	dyn3-012.cc.umanitoba.ca
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

> 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 <corefile> myprog.exe"
> 
> This will output a readable stack trace.

Great, thanks! Also, is there a way to redirect stderr under plain DOS
(ie. someone who doesn't have djgpp, bash and other such utils
installed)? Again, rhide does this so maybe it's built into djgpp
executables (like globbing)

> 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.

I know that much :) Can do I the same (symify or something similar) to
my bombed linux/sunos files (as vi lacks rhide's built in feature)? IE.
some how use the 'core' file to make a call stack?

-- 
====================================================================
Alex Demko (Alex_Demko AT mbnet DOT mb DOT ca) # Chaos Software Productions
Univ. of Manitoba Comp. Sci.        # Just released: Drip! (PC 386+)
C C++ Pascal Delphi Perl HTML Java  # http://www.mbnet.mb.ca/chaos

- Raw text -