public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Theodore A. Roth" <troth@openavr.org>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: breakpoint for avr?
Date: Wed, 14 May 2003 17:40:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.53.0305140955520.25620@knuth.amplepower.com> (raw)
In-Reply-To: <3EC26895.4090407@redhat.com>



On Wed, 14 May 2003, Andrew Cagney wrote:

:) Theodore,
:)
:) Just noticed that the AVR target doesn't provide the BREAKPOINT_FROM_PC
:) method.
:)
:) Up until now the architecture vector providing a default
:) breakpoint_from_pc (it would internal error for the AVR case). I
:) suspect, up until now, this hasn't been a problem because the AVR was
:) always remote.
:)
:) Anyway, I've just posted a patch to always require breakpoint-from-pc
:) and this is causing the AVR grief.

Can you give me a reference to that patch so I can try it?

:)
:) So, is there a breakpoint instruction, or should GDB allow targets that
:) have no breakpoint at all?

There is a BREAK instruction for some avr devices (acts as a NOP for
devices that don't have it). Since the avr is always remote, I use the
'Z' packets for setting breakpoints. I'm not sure how useful the BREAK
insn would be for gdb though. I guess the remote monitor could
intercept it some how.

How does the BREAKPOINT_FROM_PC method relate to 'Z' packets from the
remote protocol?

Ted Roth

  parent reply	other threads:[~2003-05-14 17:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14 16:02 Andrew Cagney
2003-05-14 16:56 ` Kevin Buettner
2003-05-14 17:40 ` Theodore A. Roth [this message]
2003-05-14 22:04 ` Theodore A. Roth
2003-05-15 16:19   ` Andrew Cagney
2003-05-15 16:45     ` Theodore A. Roth
2003-05-15 17:29       ` Andrew Cagney
2003-05-15 18:03         ` Theodore A. Roth
2003-05-15 18:11           ` Andrew Cagney

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=Pine.LNX.4.53.0305140955520.25620@knuth.amplepower.com \
    --to=troth@openavr.org \
    --cc=ac131313@redhat.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).