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: Tracing all 'call' instructions in a gdb session

From: Daniel Jacobowitz <drow at false dot org>
To: Thomas Glanzmann <sithglan at stud dot uni-erlangen dot de>,gdb at sources dot redhat dot com
Date: Mon, 27 Jun 2005 18:32:33 -0400
Subject: Re: Tracing all 'call' instructions in a gdb session
References: <20050627220122.GF8659@cip.informatik.uni-erlangen.de> <20050627220339.GA1457@nevyn.them.org> <20050627221010.GG8659@cip.informatik.uni-erlangen.de>

On Tue, Jun 28, 2005 at 12:10:10AM +0200, Thomas Glanzmann wrote:
> Hello,
> 
> > Sorry, GDB can't help you with this.  Not today, anyway.  You'd need
> > both tracepoints and a more flexible facility for setting breakpoints
> > automatically.
> 
> What about using objdump and grep setting a few hunderd tracepoints?
> Would that work?

Except native GDB doesn't support tracepoints, and I don't know how
it's going to cope with a breakpoint list many thousands long.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

References:
- Tracing all 'call' instructions in a gdb session
  - From: Thomas Glanzmann
- Re: Tracing all 'call' instructions in a gdb session
  - From: Daniel Jacobowitz
- Re: Tracing all 'call' instructions in a gdb session
  - From: Thomas Glanzmann

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