From: Andrew Cagney <ac131313@redhat.com>
To: Steve Watt <steve@asicdesigners.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch rfc] Add NUM_REGS pseudo regs to MIPS
Date: Mon, 21 Jul 2003 15:26:00 -0000 [thread overview]
Message-ID: <3F1C062D.2050607@redhat.com> (raw)
In-Reply-To: <200307190013.h6J0DS7B098077@oberon.asicdesigners.com>
Sigh. Something in the backtrace is still amiss.
> #2 0x080ca201 in gdbarch_register_sim_regno (gdbarch=0x82fdc48, reg_nr=90)
> at ../../combined/gdb/gdbarch.c:4078
> #3 0x08125173 in gdbsim_fetch_register (regno=90) at ../../combined/gdb/remote-sim.c:299
> #4 0x08093e0b in legacy_read_register_gen (regnum=90,
> myaddr=0xbffff140 " ñÿ¿HÃ/\bhñÿ¿î\211\f\bHÃ/\bZ")
> at ../../combined/gdb/regcache.c:727
As far as I can tell, frame_register_unwind doesn't call
legacy_read_register_gen.
> #5 0x08113891 in frame_register_unwind (frame=0x82e0f40, regnum=90,
> optimizedp=0xbffff0e8, lvalp=0xbffff0ec, addrp=0xbffff0f0, realnump=0xbffff014,
> bufferp=0xbffff140) at ../../combined/gdb/frame.c:534
> #6 0x080dbd82 in mips_get_saved_register (
> raw_buffer=0xbffff140 " ñÿ¿HÃ/\bhñÿ¿î\211\f\bHÃ/\bZ", optimizedp=0xbffff0e8,
> addrp=0xbffff0f0, frame=0x82e0f40, regnum=90, lvalp=0xbffff0ec)
> at ../../combined/gdb/mips-tdep.c:5603
I suspect some agressive tail-call optimization by GCC is involved. Can
you update your sources (so that we both have the same code) and then
configure/build gdb using:
CFLAGS="-O -g" .../configure ....
so that -O2 is disabled (or at least should be).
Andrew
next prev parent reply other threads:[~2003-07-21 15:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-19 0:13 Steve Watt
2003-07-21 15:26 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-21 22:57 Steve Watt
2003-07-21 18:20 Steve Watt
2003-07-21 22:38 ` Andrew Cagney
2003-07-07 20:01 Steve Watt
2003-07-18 22:20 ` Andrew Cagney
2003-06-16 15:35 Andrew Cagney
2003-06-16 15:44 ` Daniel Jacobowitz
2003-06-18 4:32 ` Kevin Buettner
2003-06-18 16:36 ` Andrew Cagney
2003-06-18 23:54 ` Kevin Buettner
2003-06-21 18:22 ` 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=3F1C062D.2050607@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=steve@asicdesigners.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