25 Nov
2008
25 Nov
'08
12:59
Christian Jaeger wrote:
Your best bet (short of someone going to debug it for you) really is running Gambit under gdb and see where it crashes. Just run "gdb gsc" and from there load your program as usual (assuming you're using, or know how to use, |compile-file| and |load| for your programs), or "gdb yourlinkedprogram" or "gdb gsi-script" or whatever. Then "run eventualprogramarguments" then "backtrace" when it crashed.
PS. I once wrote a script named "with-gdb-backtrace-to" which makes running apps under gdb trivial, I've now put it up here:
http://repo.or.cz/w/with-gdb-backtrace-to.git?a=blob_plain;f=with-gdb-backtr... http://repo.or.cz/w/with-gdb-backtrace-to.git
Christian.