kdb
[Top] [All Lists]

Re: dataw breakpoints

To: borislav@xxxxxxxxxxxxxxxxxxxx (Borislav Deianov)
Subject: Re: dataw breakpoints
From: slurn@xxxxxxxxxxxxxxxxxxxx (Scott Lurndal)
Date: Tue, 15 Feb 2000 09:24:32 -0800 (PST)
Cc: kdb@xxxxxxxxxxx
In-reply-to: <20000215161136.A10501@xxxxxxxxxxxxxxxxxxxxxx> from "Borislav Deianov" at Feb 15, 2000 04:11:36 PM
Sender: owner-kdb@xxxxxxxxxxx
> 
> Hi,
> 
> I'm trying to set a DATAW breakpoint (on a PIII) and can't seem to be
> able to. It always comes out as "Instruction(i)", and is not triggered
> when something writes to the given address. 
> 
> Looking at the code (1.0 for 2.3.29), there seem to be two separate
> problems:
> 
> -- kdba_parsebp saves the type of the breakpoint (1 for dataw in my
> case) in the bp_template field of the passed kdb_bp_t *bp. When
> printing the breakpoint in kdb_printbp the code never looks in the
> bp_template field, so all breakpoints are shown as "Instruction(i)".
> 
> -- It seems that kdba_allocbp should copy the info from the
> bp_template field to the newly allocated kdbhard_bp_t, so later
> kdba_installdbreg can find it there when installing the breakpoint.

I'll take a look this morning at this code.  Thanks for the heads-up.

The 2.3 version is still a bit rough around the edges.

> 
> This is just from a quick look at the code, don't feel comfortable
> enough with it to volunteer a patch.
> 
> One more question: when can we expect kdb for 2.3.4x? I have a problem
> I cannot reproduce on 2.3.29...

I'm currently (as I write this) working with 2.3.42.  There is some
problem that causes an immediate triple-fault (reset condition) that
i'm try to sort out.  More news soon.

scott

> 
> Thanks a lot,
> Borislav
> 


<Prev in Thread] Current Thread [Next in Thread>