[lkml]   [2000]   [Jul]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: SIGSEGV on fclose.
Date 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.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:57    [W:0.063 / U:81.672 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site