From: Kevin Buettner <kevinb@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] mips-tdep.c: Fix inferior function call breakage
Date: Fri, 24 Jan 2003 03:55:00 -0000 [thread overview]
Message-ID: <1030124035453.ZM29667@localhost.localdomain> (raw)
In-Reply-To: Andrew Cagney <ac131313@redhat.com> "Re: [RFA] mips-tdep.c: Fix inferior function call breakage" (Jan 23, 4:00pm)
On Jan 23, 4:00pm, Andrew Cagney wrote:
> Kevin, can you post a backtrace showing how the program came to be
> there?
#0 heuristic_proc_start (pc=268437552)
at /ocotillo2/mips64linux-021009-branch/devo/gdb/mips-tdep.c:1794
#1 0x080ead9f in find_proc_desc (pc=268437552, next_frame=0x0, cur_frame=1)
at /ocotillo2/mips64linux-021009-branch/devo/gdb/mips-tdep.c:2399
#2 0x080eaf49 in mips_init_extra_frame_info (fromleaf=0, fci=0x83f8990)
at /ocotillo2/mips64linux-021009-branch/devo/gdb/mips-tdep.c:2473
#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
#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
#7 0x080b2716 in evaluate_subexp_standard (expect_type=0x0, exp=0x8501c68,
pos=0xbffff2e4, noside=EVAL_NORMAL)
at /ocotillo2/mips64linux-021009-branch/devo/gdb/eval.c:938
#8 0x080b0cbc in evaluate_subexp (expect_type=0x0, exp=0x8501c68,
pos=0xbffff2e4, noside=EVAL_NORMAL)
at /ocotillo2/mips64linux-021009-branch/devo/gdb/eval.c:69
#9 0x080b0e5e in evaluate_expression (exp=0x8501c68)
at /ocotillo2/mips64linux-021009-branch/devo/gdb/eval.c:158
#10 0x080be66c in print_command_1 (exp=0x83f2a35 "hello()", inspect=0,
voidprint=0)
at /ocotillo2/mips64linux-021009-branch/devo/gdb/printcmd.c:926
#11 0x080be7d6 in call_command (exp=0x83f2a35 "hello()", from_tty=1)
at /ocotillo2/mips64linux-021009-branch/devo/gdb/printcmd.c:988
#12 0x0808d0f2 in do_cfunc (c=0x83fdb60, args=0x83f2a35 "hello()", from_tty=1)
at /ocotillo2/mips64linux-021009-branch/devo/gdb/cli/cli-decode.c:53
#13 0x0808e96e in cmd_func (cmd=0x83fdb60, args=0x83f2a35 "hello()",
from_tty=1)
at /ocotillo2/mips64linux-021009-branch/devo/gdb/cli/cli-decode.c:1527
...
Hmm, that's from a branch, but it happens with current sources too. If
you wish, I can generate another backtrace with current sources...
Kevin
next prev parent reply other threads:[~2003-01-24 3:55 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 [this message]
2003-01-27 19:21 ` Andrew Cagney
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=1030124035453.ZM29667@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.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