From: Michael Chastain <mec.gnu@mindspring.com>
To: pgilliam@us.ibm.com, gdb-patches@sources.redhat.com
Subject: Re: Avoid timeouts in call-sc.exp
Date: Tue, 24 Aug 2004 18:55:00 -0000 [thread overview]
Message-ID: <412B8F25.nail1SD15JH17@mindspring.com> (raw)
In-Reply-To: <200408241148.06913.pgilliam@us.ibm.com>
Paul Gilliam <pgilliam@us.ibm.com> wrote:
> Here is the $64000 question: why did GDB recognize we were in the
> outermost frame for the 32-bit case and not for the 64-bit case?
Two things at a time.
The problem in call-sc.exp is that it assumes that the inferior
program is at a well-defined location after 'return'. When that's
not true, it derails. I want to get that fixed.
The problem in gdb is that 'return' is the I/O error on fpscr.
It's yet another issue about recognizing the outermost frame
on different ports, and I'm not going to care about that now.
next prev parent reply other threads:[~2004-08-24 18:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 21:28 Paul Gilliam
2004-08-18 21:58 ` Michael Chastain
2004-08-20 10:34 ` Michael Chastain
2004-08-20 16:17 ` Paul Gilliam
2004-08-23 21:11 ` Paul Gilliam
2004-08-23 21:55 ` Michael Chastain
2004-08-24 16:15 ` Paul Gilliam
2004-08-24 17:26 ` Michael Chastain
2004-08-24 18:50 ` Paul Gilliam
2004-08-24 18:52 ` Daniel Jacobowitz
2004-08-24 18:55 ` Michael Chastain [this message]
2004-08-24 19:14 ` Paul Gilliam
2004-08-25 17:54 ` Paul Gilliam
2004-08-25 18:11 ` Michael Chastain
2004-08-25 18:21 ` Paul Gilliam
2004-08-25 18:52 ` Michael Chastain
2004-08-25 19:08 ` Paul Gilliam
2004-08-26 14:17 ` Michael Chastain
2004-08-26 16:17 ` Paul Gilliam
2004-08-26 16:26 ` Michael Chastain
2004-08-26 16:34 ` Paul Gilliam
[not found] ` <200408261227.58890.pgilliam@us.ibm.com>
[not found] ` <412E5915.8010401@gnu.org>
2004-08-31 19:30 ` Paul Gilliam
2004-08-31 20:48 ` Paul Gilliam
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=412B8F25.nail1SD15JH17@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=gdb-patches@sources.redhat.com \
--cc=pgilliam@us.ibm.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