public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Saurabh Srivastava" <saurabh@acmet.com>
To: <gdb@sources.redhat.com>
Subject: Does GDB keeps a track for Instruction Cycles?
Date: Wed, 29 Sep 2004 13:01:00 -0000	[thread overview]
Message-ID: <000d01c4a620$b53b8e80$5200a8c0@saurabh> (raw)

Hi,


I am new to this mailing list. I want your help to let me find answer to
the question 'whether GDB keeps a track for instruction cycles'.

Actually Debugging GDB was not productive enough because the points
where I made the search didn't have much to say. My search was local to
'mips' simulator.

I have looked into manual, 'Debugging with GDB' (to look for if there is
any command present), gdb internals. I got an initial impression that
GDB does not maintain records for instruction cycle.

Before proceeding any further, I thought of confirming this with gdb
mailing list.

If I am wrong and GDB keeps a track for instruction cycles then please
provide me the pointers in GDB source where it is implemented.

My curiosity about this implementation, which if exists, is that how it
is handling the extra instruction cycles caused due to breakpoints, etc.


Thanks in advance
Saurabh

                 reply	other threads:[~2004-09-29 13:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='000d01c4a620$b53b8e80$5200a8c0@saurabh' \
    --to=saurabh@acmet.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).