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: Debuging threaded applications

From: "Tavian Barnes" <tavianator at gmail dot com>
To: techgenius at gmail dot com, gdb at sourceware dot org
Date: Sat, 27 Jan 2007 14:36:20 -0700
Subject: Re: Debuging threaded applications
References: <add883140701271138g48fdcfceidd33fe490d0d06e1@mail.gmail.com> <20070127202311.GA5033@nevyn.them.org>
Reply-to: techgenius at gmail dot com

I looked in the source code.  In linux-thread-db.c, all the calls to
attach_thread and detach_thread have verbose=1.  Replacing the 1s with
0s solved the problem.

On 1/27/07, Daniel Jacobowitz <drow@false.org> wrote:

On Sat, Jan 27, 2007 at 12:38:47PM -0700, Tavian Barnes wrote:
> When debuging multi-threaded applications, is there any way to disable
> the [New Thread...] and [Thread ... exited] messages?  In a program
> that uses lots of threads, these messages get in the way, and slow
> down the debuging.  Thanks.

No, there's currently no way to do this.

--
Daniel Jacobowitz
CodeSourcery

References:
- Debuging threaded applications
  - From: Tavian Barnes
- Re: Debuging threaded applications
  - From: Daniel Jacobowitz

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