From: Daniel Jacobowitz <dan@codesourcery.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Understanding aspaces
Date: Wed, 17 Mar 2010 18:50:00 -0000 [thread overview]
Message-ID: <20100317185038.GA10403@caradoc.them.org> (raw)
In-Reply-To: <4BA122FE.7030604@vmware.com>
On Wed, Mar 17, 2010 at 11:44:14AM -0700, Michael Snyder wrote:
> Or to be more accurate, "I'm not understanding aspaces".
> A little help would be appreciated.
>
> The basic problem at the moment: software_breakpoint_inserted_here_p is
> failing to recognize the breakpoint address, because the aspace of the
> breakpoint does not match the aspace of the regcache.
>
> This is remote debugging between native linux-x86_64 and gdbserver.
Is this HEAD? I just recently fixed a similar bug.
> The register aspace, however, comes from the current ptid, and
> has num equal to some large value that varies from one run to the
> next. I'm not sure how it's derived.
Sounds like the same bug.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2010-03-17 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 18:44 Michael Snyder
2010-03-17 18:50 ` Daniel Jacobowitz [this message]
2010-03-17 19:00 ` Michael Snyder
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=20100317185038.GA10403@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.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