public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Schneider, Jan (GE51)" <Jan.Schneider@honeywell.com>
To: gdb@sources.redhat.com
Subject: x86 Hardware Breakpoints
Date: Fri, 22 Oct 2004 16:33:00 -0000	[thread overview]
Message-ID: <938F1554888BD71194E100B0D0FCD97201AAD7D2@ge51smail2.ge51.honeywell.de> (raw)

I would like to implement Hardware Breakpoints for the MPC855.
For this I currently analyze the gdb, how it works with x86 processors.
Now I look for the straight place in the gdb sources, where it stops if such
breakpoint is triggered
or rather where the gdb gets feedback of the processor that the breakpoint
has slammed.

I hope that someone can point me some helpful information.

thanks
Jan

             reply	other threads:[~2004-10-22 14:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22 16:33 Schneider, Jan (GE51) [this message]
2004-10-22 19:53 ` Dave Korn
2004-10-24 18:43 Xinan Tang

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=938F1554888BD71194E100B0D0FCD97201AAD7D2@ge51smail2.ge51.honeywell.de \
    --to=jan.schneider@honeywell.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).