Re: [gtk-list] Re: Perl/Gtk CVS 19990922
- From: CountZero <countzero cyberdeck org>
- To: gtk-list redhat com
- Subject: Re: [gtk-list] Re: Perl/Gtk CVS 19990922
- Date: Thu, 30 Sep 1999 15:40:19 -0500
Could be... I fork, exec() and then ignore... (I don't care how the children exit... they take care of
themselves.) I have set $SIG{CHLD} = 'IGNORE'; which should make my main app just go on
about it's buisness. I will test your theory though, and see what I can find out. Of course, it
will core dump even if it NEVER forks! that I know for sure, as you can run the program, and
just go straight to the Exit dialog (not activating a single widget or fork() call at all) and it will
STILL dump core (it has however made 5 calls to Gtk::Gdk::Pixmap->create_from_xpm()
at that point)
-Steve Kordik
> On 30 Sep, CountZero wrote:
> >> > PS I am getting 'Abort (core dumped)' on exit again. I have changed a load
> >> > of code so it may well be my fault but has anyone else noticed this?
> >>
> >> Well, you shouldn't be getting a core dump using Perl/Gtk: provide a test
> >> case so we can check what's wrong.
> >
> > Perl/Gtk core dumps on exit very consistantly.
> >
> > Test case?
> >
> > CSCMail: http://www.cyberdeck.org/cscmail
> >
> > It'll segfault/coredump nearly every time you exit the program.
>
> Are you sure that it is the GTK code?
>
> I had a problem like this, last week, but the problem was that the app
> was not waiting for the childs and execs/systems to exit clean.
>
> I added some sane checks before exiting and it never coredump again :-)
>
> I looked over your code, and I guess that you have a similar problem.
>
>
> -Raul Dias
[
Date Prev][Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]