From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com, Jim Blandy <jimb@redhat.com>
Subject: Re: [Fwd: Re: tdep/1155: s/390 Linux: GDB can't reselect the right frame after an inferior function call]
Date: Thu, 27 Mar 2003 21:37:00 -0000 [thread overview]
Message-ID: <20030327213715.GA19131@nevyn.them.org> (raw)
In-Reply-To: <3E836DFA.2070603@redhat.com>
On Thu, Mar 27, 2003 at 04:32:42PM -0500, Andrew Cagney wrote:
> There are two ways of handling bugs:
>
> a. the bug remains open until every last possible [un]related issue is
> resolved
>
> b. the original bug, as filed, is closed, as soon as the original
> problem is resolved. If additional problems or enhancements are
> identified, they are recorded in new separate bug reports
The original bug, as filed, said:
<quote>
If you ask GDB to make an inferior function call when the youngest
frame is a frameless function, and the selected frame is the
second-to-youngest frame, then GDB will not properly re-select the
second-to-youngest frame when the inferior call returns.
On the S/390, if a function doesn't use alloca, then the compiler just
uses the stack pointer as the frame pointer. This means that GDB's
frame_info structures use the address of the low end of the frame as
the frame base, not the high end. (The S/390 stack grows downwards.)
So, if the youngest function call hasn't allocated any stack space,
then its frame base address is equal to that of its caller. This means
that frame_find_by_id is unable to distinguish between the two.
</quote>
In what way do you see this problem as resolved?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-03-27 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 21:32 Andrew Cagney
2003-03-27 21:37 ` Daniel Jacobowitz [this message]
2003-03-27 22:23 ` Andrew Cagney
2003-03-30 16:57 ` Andrew Cagney
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=20030327213715.GA19131@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).