[9512] in The GTK GIMP ToolKit mailing list archive
[gtk-list] Re: gtk_init wierdness
daemon@ATHENA.MIT.EDU (katre)
Thu Oct 22 12:00:39 1998
From: katre <katre@mousetrap.ml.org>
To: gtk-list@redhat.com
Date: Thu, 22 Oct 1998 12:00:55 -0400 (EDT)
In-Reply-To: <Pine.LNX.3.96LJ1.1b7.981022224758.20295H-100000@ume.pht.co.jp> from "Scott Stone" at Oct 22, 98 10:48:37 pm
Resent-From: gtk-list@redhat.com
Reply-To: gtk-list@redhat.com
>
> On Thu, 22 Oct 1998, Jason A. Pfeil wrote:
>
> > What is the value of story_file_p? Trying to close a file pointer that
> > points to null is also suicidal for a program.
>
> I've noticed that closing a null pointer IS ok if you're using libc5, but
> glibc does produce the segv, as it should. Note, some older apps that
> were designed with libc5 think that it's perfectly okay to close null
> pointers, and don't check for it... it's scary :)
>
Would it still cause a crash if it's not being executed. Seriously, the only
code being executed here is the printf(), gtk_init(), and the last printf().
Why should it matter if a function that is not called tries to close a NULL
pointer?
katre
--
To unsubscribe: mail -s unsubscribe gtk-list-request@redhat.com < /dev/null
