Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>
To: gdb@sources.redhat.com
Subject: Re: Tracing all 'call' instructions in a gdb session
Date: Mon, 27 Jun 2005 22:10:00 -0000	[thread overview]
Message-ID: <20050627221010.GG8659@cip.informatik.uni-erlangen.de> (raw)
In-Reply-To: <20050627220339.GA1457@nevyn.them.org>

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?

> A profiler might be a better tool.  I bet you can get valgrind to do
> this somehow.

I thought exactly the same. I am going to ask this on the valgrind ml.
;-) But it shouldn't be a problem if valgrind simulates the call
instruction.

	Thomas


  reply	other threads:[~2005-06-27 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-27 22:01 Thomas Glanzmann
2005-06-27 22:03 ` Daniel Jacobowitz
2005-06-27 22:10   ` Thomas Glanzmann [this message]
2005-06-27 22:32     ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050627221010.GG8659@cip.informatik.uni-erlangen.de \
    --to=sithglan@stud.uni-erlangen.de \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox