lkml.org 
[lkml]   [1998]   [Jun]   [21]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
FromRoderich Schupp <>
DateSun, 21 Jun 1998 12:21:47 +0200
SubjectRe: fork() memory corruption... is this glibc2 or kernel?



Hi,
> fork() memory corruption... is this glibc2 or kernel?
Maybe it's your program :) I could reproduce the "bug" (Linux
2.1.106 on ix86, glibc-2.0.6c). However, sticking in "fflush(fp)"
just before the fork() cured it. IMHO, a fork gives you a shared
file descriptor underlying the FILE pointer fp; probably the
caching done by glibc for fread and friends doesn't cope with that.
However, I'm not sure whether it's supposed to work. A quick
glance over the Single Unix Spec v2 doesn't show any required
behaviour of open FILEs (as opposed to file descriptors) across fork.
Chhers, Roderich
--
WHAT? I thought these were stuffed peppers.  Honey, what the heck IS this??
               Whatever it is, I'm not eating it!
Roderich Schupp                 mailto:rsch@ExperTeam.de
ExperTeam GmbH                  http://www.experteam.de/
Munich, Germany                 linux:2.1.106



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

\
 
 \ /
  Last update: 2005-03-22 12:43    [from the cache]
©2003-2008