From: Andrew Cagney <ac131313@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] mips-tdep.c: Fix inferior function call breakage
Date: Mon, 27 Jan 2003 19:21:00 -0000 [thread overview]
Message-ID: <3E3586B9.9080100@redhat.com> (raw)
In-Reply-To: <1030124035453.ZM29667@localhost.localdomain>
Thanks,
> #3 0x080e0484 in gdbarch_init_extra_frame_info (gdbarch=0x8424428,
> fromleaf=0, frame=0x83f8990)
> at /ocotillo2/mips64linux-021009-branch/devo/gdb/gdbarch.c:4122
> #4 0x0809f589 in create_new_frame (addr=1099511626816, pc=268437552)
> at /ocotillo2/mips64linux-021009-branch/devo/gdb/blockframe.c:273
Things went wrong here (with the below calling the above). However, ...
> #5 0x080cd089 in run_stack_dummy (addr=268438080, buffer=0x8460058)
> at /ocotillo2/mips64linux-021009-branch/devo/gdb/infcmd.c:1002
> #6 0x080b6c90 in hand_function_call (function=0x8464a90, nargs=0,
> args=0xbffff054)
> at /ocotillo2/mips64linux-021009-branch/devo/gdb/valops.c:1762
... I've eliminated that call from "infcmd.c"!
> Hmm, that's from a branch, but it happens with current sources too. If
> you wish, I can generate another backtrace with current sources...
Yes.
Andrew
next prev parent reply other threads:[~2003-01-27 19:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 7:26 Kevin Buettner
2003-01-23 17:00 ` Daniel Jacobowitz
2003-01-23 21:00 ` Andrew Cagney
2003-01-23 22:42 ` Daniel Jacobowitz
2003-01-24 3:55 ` Kevin Buettner
2003-01-27 19:21 ` Andrew Cagney [this message]
2003-01-27 19:57 ` Kevin Buettner
2003-01-27 22:59 ` Andrew Cagney
2003-01-27 23:57 ` Kevin Buettner
2003-01-28 13:14 ` Andrew Cagney
2003-01-28 16:32 ` Kevin Buettner
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=3E3586B9.9080100@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@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