This is the mail archive of the gdb@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: gdb and cloned process

From: Daniel Jacobowitz <drow at false dot org>
To: Lukasz Lempart <llempart at gmail dot com>
Cc: gdb at sourceware dot org
Date: Wed, 22 Oct 2008 23:05:48 -0400
Subject: Re: gdb and cloned process
References: <4ced24c0810221709u17575bf3s73994724c456e956@mail.gmail.com>

On Wed, Oct 22, 2008 at 05:09:32PM -0700, Lukasz Lempart wrote:
> How does gdb (through libthread_db) figure out what threads belong to a process?

The thread library maintains an internal list of threads.  If you've
cloned the process, without telling the C library about that, you're
going to end up with the same list of threads; so the behavior you
describe is not surprising.

> Is there currently a way to disable thread debugging in gdb?

Not really.  You might be able to preload a dummy libthread_db.so.1
that always failed to detect new threads.

-- 
Daniel Jacobowitz
CodeSourcery

Follow-Ups:
- Re: gdb and cloned process
  - From: Lukasz Lempart
- Re: gdb and cloned process
  - From: Michael Snyder

References:
- gdb and cloned process
  - From: Lukasz Lempart

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