Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "mohanlal jangir" <mohanlaljangir@hotmail.com>
To: "Andrew Cagney" <cagney@gnu.org>
Cc: <gdb@sources.redhat.com>
Subject: Re: hardware support for gdb?
Date: Tue, 17 Feb 2004 04:49:00 -0000	[thread overview]
Message-ID: <LAW11-OE16LPEhGD1Xy00036928@hotmail.com> (raw)
In-Reply-To: <4031535A.7080500@gnu.org>

> >
> > Really!! Does even single stepping also not require any hardware
support?
>
> I'm not sure what you mean by hardware support.  The instruction set
> architecture needs to provide a breakpoint instruction.  A single-step
> mechanism is useful but not an absolute requirement - GDB can use
> software singlestep (although I suspect that code has bitrotten).
>
> Andrew
>

Thanks Andrew for your prompt replies. I was reading an article on "how gdb
works". This is a paragraph from that:

The Remote Serial Protocol's step command is a bit more challenging,
especially when the target processor doesn't provide a "trace bit" or
similar functionality (For example, Motorola 683xx processors contain the
ability to trap on instruction execution and/or changes in program flow;
this feature is controlled by the "trace enable" bits, T1 and T0, in the
processor's status register). In these cases, the only alternative is for
the stub to disassemble the instruction about to be executed so that it can
determine where the program is going to go next.

What I understood from this paragraph is that, if a target processor provide
"trace bit" kind of functionality, gdb developer's life is easier otherwise
he has to do some more work(disassembling of instruction). Am I right? Could
you please explain a little about "trace bit" or similar functionality? Is
it the breakpoint instruction, you mentioned about?

Regards
Mohanlal


  reply	other threads:[~2004-02-17  4:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13 10:47 mohanlal jangir
2004-02-13 14:55 ` Andrew Cagney
2004-02-16  4:06   ` mohanlal jangir
2004-02-16 23:33     ` Andrew Cagney
2004-02-17  4:49       ` mohanlal jangir [this message]
2004-02-17 13:56         ` Bill Gatliff
2004-02-17 20:04           ` Vijay Kamarshi
2004-02-18 14:25             ` Bill Gatliff
2004-02-18 16:51               ` Vijay Kamarshi
2004-02-17 15:12         ` Peter Barada
2004-02-17  5:12 Atul Talesara

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=LAW11-OE16LPEhGD1Xy00036928@hotmail.com \
    --to=mohanlaljangir@hotmail.com \
    --cc=cagney@gnu.org \
    --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