From: Ben Johnson <ben@blarg.net>
To: gdb@sources.redhat.com
Subject: Re: how are debug registers supposed to work?
Date: Wed, 17 Sep 2003 00:30:00 -0000 [thread overview]
Message-ID: <20030916173040.B24214@blarg.net> (raw)
In-Reply-To: <20030828174129.B9184@blarg.net>; from ben@blarg.net on Thu, Aug 28, 2003 at 05:41:29PM -0700
I found the problem. The addresses I'm attempting to use are logical
addresses, not linear. The (2.0) kernel data segment's base address is
0xc0000000, so in order to get a linear address I have to add that base
address to it.
altered code that's now trapping in the right place:
schedule()
{
...
static unsigned long has_run = 1;
static unsigned long has_run_2 = 0;
if( ! has_run && jiffies > 7000 )
{
has_run = 1;
has_run_2 = 0;
/* setup the debug registers */
asm ("movl %%cr4, %%edx\n" /* debug extensions */
" orl $0x8, %%edx\n"
" movl %%edx, %%cr4\n"
" movl %0, %%db0\n" /* push into db regs */
" movl %1, %%db7\n"
" lgdt 0x00106852\n" /* pentium may need this */
: /* no output */
:"a"(0xc0000000 + ((unsigned long)&has_run_2)),
"b"(0x000f2202)
/*"m"((((char *)&gdt)-6))*/
:"%edx"
);
}
if( has_run && ! has_run_2 ) /* debug reg generate exception */
{
/* whatever */
has_run_2 = 0xffffffff
}
...
}
I'm sure the debug extensions aren't needed. I put in the lgdt
instruction because I read section in 18.17.4 of Intel's Software
Development Manual (Volume 3) that it may help Pentium processors
recognize breakpoints. no other processors need that though.
- Ben
prev parent reply other threads:[~2003-09-17 0:30 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
2003-09-04 0:17 ` Ben Johnson
2003-09-17 0:30 ` Ben Johnson [this message]
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=20030916173040.B24214@blarg.net \
--to=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