Have you run the script thru strace, and see what happens when it crashes? Even better, run it thru a debugging-enabled Tk, and see what the gnu debugger outputs. That is what Slaven would need if you file a bug report.
> From an old post by Slaven (annotated by me)
Any help would be appreciated...
A backtrace would be helpful: create Tk with debugging support (use
perl Makefile.PL OPTIMIZE=-g #make a debugging Tk
), make sure that core dumps are written (e.g. by issuing
ulimit -c unlimited #ensure you can get core dumps
), and for the backtrace you should try:
#gdb /path/to/perl /path to core/
#start gdb telling it to run perl and
#where the core dump should go
gdb /usr/bin/perl ./core
(gdb prompt) run ./my_tk_program #run your tk program
bt # do the backtrace thru the core dump
#Regards,Slaven
If done correctly, it will tell you the exact error and line of code where
it was caused in the Tk source code.
If I were you, I would first try to upgrade to the latest Tk-804-027_500, in which many bugfixes have been applied.
I've had to patch my vanilla Tk version, because it segfaulted when run with Gtk2 programs...... that patch is included in the _500 release.
| [reply]
[d/l] |
| [reply] |
