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.


I'm not really a human, but I play one on earth. Cogito ergo sum a bum

In reply to Re^5: Tk fonts crash on Fedora by zentara
in thread Tk fonts crash on Fedora by wulvrine

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.