However, eventhough we have set the "-g" flag to gcc in the Makefile to
provide symbols for the dubugger, we don't get any symbols for the
innermost elements of the stack trace. Without these symbols, we can not
discover the cause of the segmentation fault.
We have spent the last several days trying to figure out how to get this
symbol information. Typically, BSDI tech support doesn't even understand
what we are asking for. Out of desperation, I am apealing to this list
for any hints or suggestions for steps we might take to get the missing
symbols.
Also, I have tried versions 2.1.7 and 2.1.8 in addition to the current
2.1.9, and they all produce the same results.
I noticed a post from Richard G. Duvall <rgduvall@harborside.com> on April
24 describing what seems to be the same execution problem on BSDI 3.0.
Perhaps a solution to my problem will solve his problem as well.
The stack trace:
(gdb) run
Starting program: /usr/src/scotty-2.1.9/unix/./scotty
Program received signal SIGSEGV, Segmentation fault.
0xa0001888 in ?? ()
(gdb) bt
#0 0xa0001888 in ?? ()
#1 0x1d40e3 in ?? ()
#2 0x1d4971 in ?? ()
#3 0x1e4660 in ?? ()
#4 0x3218d in Tcl_LoadCmd ()
#5 0x2cef in TclInvokeStringCommand ()
#6 0x1d86d in TclExecuteByteCode ()
#7 0x3615 in Tcl_EvalObj ()
#8 0x3363 in Tcl_Eval ()
#9 0x4937 in Tcl_GlobalEval ()
#10 0x38342 in Tcl_PkgRequire ()
#11 0x1209 in Tcl_AppInit (interp=0x8c000) at ./../unix/scotty.c:96
#12 0x1438 in main (argc=1, argv=0xefbfda94) at ./../unix/scotty.c:179
-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.