Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com, jimb@redhat.com, ac131313@redhat.com,
	saurabh.verma@codito.com, ankit.thukral@codito.com,
	mark.newman@lmco.com
Subject: Tracepoints with shared lib. support.
Date: Wed, 01 Oct 2003 10:59:00 -0000	[thread overview]
Message-ID: <1065006023.3808.300.camel@numenor.codito.co.in> (raw)
In-Reply-To: <20030930125017.GA23342@nevyn.them.org>

hi all, 

 Another query i had was regarding tracepoints on shared library
symbols. That would also have to be handled in a manner similar to the
way in which the breakpoints for shared libraries have been implemented.
I wonder if we need internal breakpoints on the shared library event
handling which would then take care of mapping the addresses to the
actual addresses because with the current status of tracepoints the
addresses do not get mapped to the actual addresses. So if we had a
tracepoint on a function in a shared library would we then not be
increasing the number of halts in the actual execution of the program. 


regards
Ramana


  parent reply	other threads:[~2003-10-01 10:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-30 12:50 Tracepoints on gdb/gdbserver Ramana Radhakrishnan
2003-09-30 13:06 ` Daniel Jacobowitz
2003-09-30 14:00   ` Ramana Radhakrishnan
     [not found]   ` <vt2u16tnbjr.fsf@zenia.home>
2003-10-01  4:44     ` Ramana Radhakrishnan
2003-10-01 10:59   ` Ramana Radhakrishnan [this message]
2003-10-01 14:48     ` Tracepoints with shared lib. support 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=1065006023.3808.300.camel@numenor.codito.co.in \
    --to=ramana.radhakrishnan@codito.com \
    --cc=ac131313@redhat.com \
    --cc=ankit.thukral@codito.com \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=mark.newman@lmco.com \
    --cc=ramana@codito.com \
    --cc=saurabh.verma@codito.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