Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: Orjan Friberg <orjan.friberg@axis.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: recurse.exp: watch on local variable that goes out of scope
Date: Thu, 22 Jul 2004 19:19:00 -0000	[thread overview]
Message-ID: <6654-Thu22Jul2004221755+0300-eliz@gnu.org> (raw)
In-Reply-To: <40FF8C69.8050408@axis.com> (message from Orjan Friberg on Thu, 22 Jul 2004 11:44:09 +0200)

> Date: Thu, 22 Jul 2004 11:44:09 +0200
> From: Orjan Friberg <orjan.friberg@axis.com>
> 
> Breakpoint 4, i386_stopped_data_address () at ../../src/gdb/i386-nat.c:576
> 576       dr_status_mirror = I386_DR_LOW_GET_STATUS ();
> 
> Inside i386_stopped_data_address dr_status_mirror = 0xffff4ff1, which satisfies 
> the condition for I386_DR_WATCH_HIT (i) for i == 0.  The reported address is 
> 0xbffff488 (the address of local variable b).

So it sounds like your low-level target-side support misbehaves in
this case: I386_DR_LOW_GET_STATUS should map into a system call that
returns the contents of the DR6 debug register.  If the returned value
says that one of the watched addresses was written to, there's nothing
GDB can do except report that and act accordingly.

> I fail to see why these two cases should be different.

Neither do I, but I'm not an expert for your target platform.


  reply	other threads:[~2004-07-22 19:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-20 14:37 Orjan Friberg
2004-07-20 19:37 ` Eli Zaretskii
2004-07-22  9:44   ` Orjan Friberg
2004-07-22 19:19     ` Eli Zaretskii [this message]
2004-07-23  9:23       ` Orjan Friberg
2004-07-28 15:52         ` Orjan Friberg

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=6654-Thu22Jul2004221755+0300-eliz@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=orjan.friberg@axis.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