This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Understanding aspaces
- From: Michael Snyder <msnyder at vmware dot com>
- To: "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Wed, 17 Mar 2010 11:44:14 -0700
- Subject: Understanding aspaces
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.
It seems like the breakpoint aspace comes from the sal, which is
assigned by get_current_source_symtab_and_line to come from
current_source_pspace. current_source_pspace->aspace->num == 1.
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.
Any words of wisdom?
Thanks,
Michael