This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: exp/1155: s/390 Linux: GDB can't reselect the right frame afteran inferior function call
- From: Andrew Cagney <ac131313 at redhat dot com>
- To: cagney at redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 27 Mar 2003 21:08:01 -0000
- Subject: Re: exp/1155: s/390 Linux: GDB can't reselect the right frame afteran inferior function call
- Reply-to: Andrew Cagney <ac131313 at redhat dot com>
The following reply was made to PR tdep/1155; it has been noted by GNATS.
From: Andrew Cagney <ac131313 at redhat dot com>
To: Jim Blandy <jimb at redhat dot com>
Cc: gdb-gnats at sources dot redhat dot com, Elena Zannoni <ezannoni at redhat dot com>
Subject: Re: exp/1155: s/390 Linux: GDB can't reselect the right frame after
an inferior function call
Date: Thu, 27 Mar 2003 16:06:55 -0500
> No.
>>
>> The problem is that the legacy dummy frame code matches either SP or
>> FP when trying to re-locate a saved frame. It should instead match
>> just a single frame ID.
>>
>> Please see save_dummy_frame_tos() and unwind_dummy_id().
>
>
> Are you sure?
Yes.
> I see that save_inferior_status saves the ID of main's frame in
> inf_status->selected_frame_id, and then restore_inferior_status passes
> that ID through to restore_selected_frame, which then calls
> frame_find_by_id, and returns marker1's frame.
>
> The dummy frame is properly popped, and is long gone before any of
> this happens. Neither of the two methods you mentioned are involved
> at all.
Perhaphs that is the problem?
Andrew