in reply to Segmentation fault at exit on Solaris 5.6.1 if require Tk instead of use

Works fine for me
perl -Mstrict -we"eval{require Tk;import Tk;1} or die $@;tkinit()->But +ton(-text=>1,-command=>sub{exit})->pack;MainLoop();" # or perl -Mstrict -we'eval{require Tk;import Tk;1} or die $@;tkinit()->But +ton(-text=>1,-command=>sub{exit})->pack;MainLoop();'
On lastest 5.6 (Tk 800.023) and 5.8 (Tk 800.024) ActivePerl on Win2000SP3.

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

  • Comment on Re: Segmentation fault at exit on Solaris 5.6.1 if require Tk instead of use
  • Download Code

Replies are listed 'Best First'.
Re: Re: Segmentation fault at exit on Solaris 5.6.1 if require Tk instead of use
by tommyw (Hermit) on Jun 13, 2003 at 10:06 UTC

    I only get the callback called exit messages if I give exit an non-zero parameter. See what happens if you use sub{exit 1}

    --
    Tommy
    Too stupid to live.
    Too stubborn to die.

      Makes no difference (which is what should happen). Where is the message coming from? Which version of Tk you got man?

      MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
      I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
      ** The third rule of perl club is a statement of fact: pod is sexy.

        800.024 in both cases.

        The Solaris version is freshly installed from CPAN, the Mandrake from the RPMs

        Ah, yes. I've found the location of the message now:

        Binary file ./5.8.0/i386-linux-thread-multi/CORE/sperl.o matches Binary file ./5.8.0/i386-linux-thread-multi/CORE/libperl.so matches
        Maybe I ought to rebuild my linux perl...

        --
        Tommy
        Too stupid to live.
        Too stubborn to die.