Re: SIGSEGV on fclose

From: Andreas Schwab (schwab@suse.de)
Date: Fri Jul 14 2000 - 05:48:34 EST


"Andi Kleen" <ak@suse.de> writes:

|> On Thu, Jul 13, 2000 at 08:51:48AM -0700, Ulrich Drepper wrote:
|> > Manfred Spraul <manfred@colorfullife.com> writes:
|> >
|> > > I assume that the other unices store a magic number within the stream
|> > > structure, but that's ugly and doesn't guarantee an error message: you
|> > > replace a 100% sigsegv with a rare race - I prefer the sigsegv.
|> >
|> > Can we all stop this nonsense now. Manfred's comment summarizes the
|> > situation pretty well. One of the basic design rules of glibc is to
|> > crash early whenever something is wrong since all workarounds (like in
|> > this case) never have a 100% chance to survive.
|>
|> The original poster passed it a NULL pointer though, not a random pointer.

fclose requires a valid FILE object pointer, and NULL isn't among them.
Case closed.

Andreas.

-- 
Andreas Schwab                                  "And now for something
SuSE Labs                                        completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Sat Jul 15 2000 - 21:00:19 EST