Re: SIGSEGV on fclose.

From: David Woodhouse (dwmw2@infradead.org)
Date: Thu Jul 13 2000 - 04:05:28 EST

Next message: Tom Leete: "Re: Object Oriented Linux"
Previous message: Bjarne Blichfeldt: "SIGSEGV on fclose."
In reply to: Bjarne Blichfeldt: "SIGSEGV on fclose."
Next in thread: matt@theBachChoir.org.uk: "Re: SIGSEGV on fclose."
Reply: matt@theBachChoir.org.uk: "Re: SIGSEGV on fclose."
Reply: Mads Bondo Dydensborg: "Re: SIGSEGV on fclose."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

bbl@dk.damgaard.com said:
> in case you wonder: the problem arises from a program that closes a
> file twice because it does not know that the file is allready closed.

Don't do that then.

Read the man page:
... any further access (including another call to fclose()) to
the stream results in undefined behaviour.

Returning SIGSEGV is permitted as 'undefined behaviour'. Just consider
yourself lucky it didn't format your hard drive, pee on the carpet, and/or
start global thermonuclear war.

-- dwmw2

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

Next message: Tom Leete: "Re: Object Oriented Linux"
Previous message: Bjarne Blichfeldt: "SIGSEGV on fclose."
In reply to: Bjarne Blichfeldt: "SIGSEGV on fclose."
Next in thread: matt@theBachChoir.org.uk: "Re: SIGSEGV on fclose."
Reply: matt@theBachChoir.org.uk: "Re: SIGSEGV on fclose."
Reply: Mads Bondo Dydensborg: "Re: SIGSEGV on fclose."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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