mitchell wrote:
I would recompile Scintilla and SciTE with the DEBUG=1 option, then run 'gdb SciTE', press 'r' and enter to run SciTE, and if it still segfaults, gdb will let you know and you can enter the 'back' command to show a backtrace of what happened.
Thanks Mitchell. I did compile with DEBUG=1, and followed the steps above, but I did not get a segfault while executing a tool - nothing did happen - but I did get a "double free or corruption" when I exited SciTE. The results of 'back' were vague and useless, showing a few unidentified addresses and some with system names such as 'libc.so.6'
So now I have to double check my changes very carefully and if that is fruitless come up with a way to debug my changes.
I've heard of Insight, a gdb GUI; I wonder if it exists for Linux / Mandriva.
April _______________________________________________ Scite-interest mailing list [email protected] http://mailman.lyra.org/mailman/listinfo/scite-interest
