From: Andrew Cagney <ac131313@redhat.com>
To: Ben Johnson <ben@blarg.net>
Cc: gdb@sources.redhat.com
Subject: Re: how are debug registers supposed to work?
Date: Wed, 03 Sep 2003 22:55:00 -0000 [thread overview]
Message-ID: <3F567176.1000100@redhat.com> (raw)
In-Reply-To: <20030828174129.B9184@blarg.net>
> So, the CPU is generating a debug exception, and I am catching it. it's
> just not happening when I want or expect it to happen. The same thing
> happens for program instruction fetches. It doesn't break.
>
> I stuck in all the wbinvd instructions thinking it might be a cache
> issue. I have yet to turn the cache off. it seems to me though that I
> should be getting some exception with or without the cache enabled.
>
> What am I doing wrong? anyone know? who knows how to use these
> registers?
Just a thought, you're not fighting a user space process playing with
those registers?
The other is to look at GDB using hardware debug registers on a user
process.
Andrew
next prev parent reply other threads:[~2003-09-03 22:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 0:41 Ben Johnson
2003-09-03 22:55 ` Andrew Cagney [this message]
2003-09-04 0:17 ` Ben Johnson
2003-09-17 0:30 ` Ben Johnson
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=3F567176.1000100@redhat.com \
--to=ac131313@redhat.com \
--cc=ben@blarg.net \
--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