This is the mail archive of the gdb-patches@sourceware.org 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: Workaround for glibc/BZ5983: following a child fork shows stale parent threads in the child.

From: Pedro Alves <pedro at codesourcery dot com>
To: Doug Evans <dje at google dot com>
Cc: gdb-patches at sourceware dot org
Date: Tue, 19 May 2009 10:56:45 +0100
Subject: Re: Workaround for glibc/BZ5983: following a child fork shows stale parent threads in the child.
References: <200905181813.48596.pedro@codesourcery.com> <e394668d0905182326r7e481761o28d5445c9362bc05@mail.gmail.com>

On Tuesday 19 May 2009 07:26:07, Doug Evans wrote:
> This works, but only because of an assumption of the strlen including
> the trailing NUL in "Tgid:" consuming the TAB between "Tgid:" and the
> number.
> We should probably document that (or make the parsing more robust).

You've lost me somewhere around the "assumption of the strlen including
the trailing NUL".  The tab/space is consumed by strtoul.

-- 
Pedro Alves

References:
- Workaround for glibc/BZ5983: following a child fork shows stale parent threads in the child.
  - From: Pedro Alves
- Re: Workaround for glibc/BZ5983: following a child fork shows stale parent threads in the child.
  - From: Doug Evans

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