This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: how are debug registers supposed to work?

From: Andrew Cagney <ac131313 at redhat dot com>
To: Ben Johnson <ben at blarg dot net>
Cc: gdb at sources dot redhat dot com
Date: Wed, 03 Sep 2003 18:55:50 -0400
Subject: Re: how are debug registers supposed to work?
References: <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

Follow-Ups:
- Re: how are debug registers supposed to work?
  - From: Ben Johnson

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]