This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: libiberty/pex-unix vfork abuse?

From: Andreas Schwab <schwab at suse dot de>
To: "Dave Korn" <dave dot korn at artimi dot com>
Cc: "'Ian Lance Taylor'" <iant at google dot com>, <gcc at gcc dot gnu dot org>
Date: Fri, 07 Dec 2007 21:51:51 +0100
Subject: Re: libiberty/pex-unix vfork abuse?
References: <05ea01c838e3$001b9b40$2e08a8c0@CAM.ARTIMI.COM> <m31w9yqw3z.fsf@localhost.localdomain> <060401c838f3$f6333aa0$2e08a8c0@CAM.ARTIMI.COM>

"Dave Korn" <dave.korn@artimi.com> writes:

>   Perhaps we could work around this case by setting environ in the parent
> before the vfork call and restoring it afterward, but we'd need kind of
> serialisation there,

Do we?  vfork should block the parent until the child calls execve or
exit.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Follow-Ups:
- RE: libiberty/pex-unix vfork abuse?
  - From: Dave Korn

References:
- libiberty/pex-unix vfork abuse?
  - From: Dave Korn
- Re: libiberty/pex-unix vfork abuse?
  - From: Ian Lance Taylor
- RE: libiberty/pex-unix vfork abuse?
  - From: Dave Korn

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]