Re: [gtk-list] Re: gtk_init wierdness

["Jason A. Pfeil" <pfeil nu cs fsu edu>]

If I remember right, you said that it crashed without the #ifdef in place
and didn't crash with the #ifdef in place...  Well, the #ifdef jumps over
the fclose() call, but without the #ifdef, it will execute the fclose()
call.

--Jason

On Thu, 22 Oct 1998, katre wrote:

> > 
> > 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
> 
> 

-------------------------------------------------------------------------------
Jason A. Pfeil, Computer Science Graduate Student      101 Carothers Hall
http://www.cs.fsu.edu/~pfeil			       C3527 University Center
pfeil@cs.fsu.edu				       (850)644-8014