From: Randolph Chung <randolph@tausq.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Infinite backtraces...
Date: Fri, 03 Dec 2004 18:03:00 -0000 [thread overview]
Message-ID: <20041203180324.GE6359@tausq.org> (raw)
In-Reply-To: <20041203165430.GC16491@adacore.com>
> > yeah, but i would have expected that you should get an error when
> > unwinding from 0 ("Cannot find bounds of current function ..."). this
> > should automatically stop the backtrace.
> >
> > would you mind sending me the output of "info reg" frame frame 5 and 6,
> > "maint print unwind __pthread_create_system" and "disassemble
> > __pthread_create_system"?
argh, i was wrong... the stub unwinder handles the case when pc == 0,
and then it assumes that the rp doesn't get modified by default.
there's also a bug in the outer __pthread_create_system frame; the stub
unwinder doesn't set the rp appropriately. can you try the attached
patch? it should convert your infinite backtrace into an error ;-)
randolph
2004-12-03 Randolph Chung <tausq@debian.org>
* hppa-tdep.c (hppa_stub_frame_unwind_cache): Set RP appropriately
for export stub frames.
Index: hppa-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/hppa-tdep.c,v
retrieving revision 1.182
diff -u -p -r1.182 hppa-tdep.c
--- hppa-tdep.c 23 Nov 2004 21:05:20 -0000 1.182
+++ hppa-tdep.c 3 Dec 2004 17:56:56 -0000
@@ -2119,8 +2120,9 @@ hppa_stub_frame_unwind_cache (struct fra
if (u && u->stub_unwind.stub_type == EXPORT)
{
info->saved_regs[HPPA_PCOQ_HEAD_REGNUM].addr = info->base - 24;
+ info->saved_regs[HPPA_RP_REGNUM].addr = info->base - 24;
return info;
}
}
next prev parent reply other threads:[~2004-12-03 18:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 22:46 Joel Brobecker
2004-12-02 23:13 ` Joel Brobecker
2004-12-03 2:43 ` Randolph Chung
2004-12-03 2:57 ` Joel Brobecker
2004-12-03 4:53 ` Randolph Chung
2004-12-03 19:36 ` Joel Brobecker
2004-12-03 18:03 ` Randolph Chung [this message]
2004-12-03 18:20 ` Joel Brobecker
2004-12-03 18:22 ` Randolph Chung
2004-12-06 7:25 ` Randolph Chung
2004-12-07 10:07 ` Joel Brobecker
2004-12-07 16:31 ` Randolph Chung
2004-12-07 16:37 ` Joel Brobecker
2004-12-07 16:52 ` Randolph Chung
2004-12-08 1:51 ` Randolph Chung
2004-12-12 16:36 ` [commit] Move zero PC check to frame.c; Was: " Andrew Cagney
2004-12-03 18:22 ` Joel Brobecker
2004-12-06 4:15 ` Randolph Chung
2004-12-07 9:40 ` Joel Brobecker
2004-12-03 18:28 ` Andrew Cagney
2004-12-03 18:49 ` Joel Brobecker
2004-12-03 19:26 ` Andrew Cagney
2004-12-03 20:19 ` Joel Brobecker
2004-12-03 21:44 ` Andrew Cagney
2004-12-03 22:16 ` Joel Brobecker
2004-12-03 22:23 ` Daniel Jacobowitz
2004-12-03 22:25 ` Joel Brobecker
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=20041203180324.GE6359@tausq.org \
--to=randolph@tausq.org \
--cc=brobecker@adacore.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