Mail Archives: djgpp/1996/08/29/21:38:14
Mike Marcelais wrote:
>
> Is that the secret on how symify works...you need the garbage on the screen?
>
> So how do you get symify to help you out when the machine dumps that cool
> garbage but completely freezes and hozes the dos box that you ran the program
> in. [Or the entire machine, if you aren't running under Windows]
Use 'redir' to redirect your program's stderr to a file. The register dump
will be saved in that file, which you can then use symify on once you reboot
the computer. Symify has options to both read from a file and write its
output to a file (so you can post it here, for example).
Example:
> redir -e errors.dmp myprog ...
[crash, then reboot]
> symify -i errors.dmp -o symify.dmp myprog
More details on using symify can be found in section 9.2 of the FAQ.
BTW, have you tried running your program under a debugger like gdb? At the
very least, setting a breakpoint near where the crash happens and stepping
through the code might give you some clues as to what's going on, even if
the computer still freezes when the crash occurs.
A reminder: when you do isolate the code fragment that's causing your
crash, please post it here as well as the core dump file from symify if
you can't figure out what's wrong yourself. :)
John
--
Anything that happens, happens.
Anything that, in happening, causes something else to happen, causes
something else to happen.
Anything that, in happening, causes itself to happen again, happens again.
It doesn't necessarily do it in chronological order, though.
--- Douglas Adams
- Raw text -