Re: crash reports: symify

[Salvador E. T. <sal...@in...>]

J.B. Lethbridge wrote:

>Dear Set:
>
>I hope this is as interesting to you as to me! I also hope it means more
>to you than it does to me!
>
>As per your instructions, here are the reports from symify:
>There are two analyses.
>
>
>First editor.exe compiled from a plain ./configure
>  
>
[snip]

>Second editor.exe compiled without the debug library (deleted)
>  
>
[snip]

:-( lamentably looks like these tracebacks are bogus because of the lack 
of enough debug info.
If you have some more time to spend on it please try doing it: (assuming 
the shell is bash)

Go to the directory where both are uncompressed, the following variables 
will force debug info in the binary:

$ export CFLAGS="-O2 -Wall -gstabs+3"
$ export CXXFLAGS="-O2 -Wall -gstabs+3"
$ cd tvision
$ ./configure ; make

Here change to root

# make install

And now back to the user

$ cd ../setedit
$ ./configure ; make
$ cd makes

Here you can run ./editor.exe and get a trace of the crash or you can:

$ gdb editor.exe
(gdb) run
It will start and crash then just do:
(gdb) backtrace

It will print the backtrace with the meaning of each symbol, you can 
copy/paste it.

Regards, SET

-- 
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Visit my home page: http://welcome.to/SetSoft or
http://www.geocities.com/SiliconValley/Vista/6552/
Alternative e-mail: se...@co... se...@ie... 
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA Phone: +(5411) 4759 0013