Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Paul Gilliam <pgilliam@us.ibm.com>
Cc: gdb-patches@sources.redhat.com,
	Michael Chastain <mec.gnu@mindspring.com>
Subject: Re: Avoid timeouts in call-sc.exp
Date: Tue, 24 Aug 2004 18:52:00 -0000	[thread overview]
Message-ID: <20040824185203.GA17045@nevyn.them.org> (raw)
In-Reply-To: <200408241148.06913.pgilliam@us.ibm.com>

On Tue, Aug 24, 2004 at 11:48:06AM -0700, Paul Gilliam wrote:
> Here is a diff between the two logs from where their difference is 
> non-trivial:
> 
> < Running target unix/-m32
> ---
> > Running target unix/-m64
> 
> 94,95c94,95
> < "finish" not meaningful in the outermost frame.
> < (gdb) FAIL: gdb.base/call-sc.exp: finish foo; return call-sc-tc
> ---
> > Run till exit from #0  main () at ./gdb.base/call-sc.c:78
> > FAIL: gdb.base/call-sc.exp: finish foo; return call-sc-tc (timeout)
> 
> 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?  Is main() 
> not the outermost frame for ppc64 but is for ppc32?  Guess I'll have to 
> break-down and check the API's.

Probably GDB is confused about main and ".main"...

-- 
Daniel Jacobowitz


  reply	other threads:[~2004-08-24 18:52 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 [this message]
2004-08-24 18:55             ` Michael Chastain
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=20040824185203.GA17045@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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