This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB 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: getpid after vfork broken in recent glibc

From: Andreas Schwab <schwab at suse dot de>
To: Eli Zaretskii <eliz at elta dot co dot il>
Cc: Daniel Jacobowitz <drow at false dot org>, cagney at gnu dot org,Ulrich dot Weigand at de dot ibm dot com, gdb at sources dot redhat dot com
Date: Tue, 09 Mar 2004 14:14:23 +0100
Subject: Re: getpid after vfork broken in recent glibc
References: <OF1553E6EB.11E0F0CB-ONC1256E51.0068BC37@de.ibm.com><404D2EB9.10607@gnu.org> <20040309025255.GA11922@nevyn.them.org><ud67msey0.fsf@elta.co.il>

Eli Zaretskii <eliz@elta.co.il> writes:

> How about if glibc did us a small favor and invalidated its cached
> PID on a vfork?

This is about to be fixed now.

Andreas.

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

References:
- getpid after vfork broken in recent glibc
  - From: Ulrich Weigand
- Re: getpid after vfork broken in recent glibc
  - From: Andrew Cagney
- Re: getpid after vfork broken in recent glibc
  - From: Daniel Jacobowitz
- Re: getpid after vfork broken in recent glibc
  - From: Eli Zaretskii

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