* Understanding aspaces
@ 2010-03-17 18:44 Michael Snyder
2010-03-17 18:50 ` Daniel Jacobowitz
0 siblings, 1 reply; 3+ messages in thread
From: Michael Snyder @ 2010-03-17 18:44 UTC (permalink / raw)
To: gdb
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Understanding aspaces
2010-03-17 18:44 Understanding aspaces Michael Snyder
@ 2010-03-17 18:50 ` Daniel Jacobowitz
2010-03-17 19:00 ` Michael Snyder
0 siblings, 1 reply; 3+ messages in thread
From: Daniel Jacobowitz @ 2010-03-17 18:50 UTC (permalink / raw)
To: Michael Snyder; +Cc: gdb
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Understanding aspaces
2010-03-17 18:50 ` Daniel Jacobowitz
@ 2010-03-17 19:00 ` Michael Snyder
0 siblings, 0 replies; 3+ messages in thread
From: Michael Snyder @ 2010-03-17 19:00 UTC (permalink / raw)
To: Michael Snyder, gdb
Daniel Jacobowitz wrote:
> 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.
Must be. I'm a few weeks back from HEAD.
Thanks.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-03-17 19:00 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-03-17 18:44 Understanding aspaces Michael Snyder
2010-03-17 18:50 ` Daniel Jacobowitz
2010-03-17 19:00 ` Michael Snyder
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox