From: Randolph Chung <randolph@tausq.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/hppa/rfa] unwind fix for functions with no debug info
Date: Wed, 03 Nov 2004 22:37:00 -0000 [thread overview]
Message-ID: <20041103223711.GG4249@tausq.org> (raw)
In-Reply-To: <41895A80.1090500@gnu.org>
> Ok for 6.3 and mainline with a comment/change log tweak:
>
> The convention is for the ChangeLog to record what was changed while the
> code records why it was changed.
will do. thanks.
I'm still looking at another aspect of this problem:
For example, in this backtrace:
(gdb) bt
#0 0x406510a8 in Tcl_Finalize () from /usr/lib/libtcl8.4.so.0
#1 0x40650de0 in Tcl_Exit () from /usr/lib/libtcl8.4.so.0
#2 0x40131224 in exp_new_i_simple () from /usr/lib/libexpect5.42.so.1
#3 0x406273b8 in TclInvokeStringCommand () from /usr/lib/libtcl8.4.so.0
#4 0x40628730 in TclEvalObjvInternal () from /usr/lib/libtcl8.4.so.0
#5 0x406293e8 in Tcl_EvalEx () from /usr/lib/libtcl8.4.so.0
#6 0x406297bc in Tcl_Eval () from /usr/lib/libtcl8.4.so.0
#7 0x00010bc0 in main ()
at frame #2, 0x40131224 is not actually in exp_new_i_simple, but in
another function with no recorded name. this backtrace is confusing;
possibly we should show "#2 0x40131224 in ??? from ..." instead?
thoughts?
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next prev parent reply other threads:[~2004-11-03 22:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 17:48 Randolph Chung
2004-11-03 22:24 ` Andrew Cagney
2004-11-03 22:37 ` Randolph Chung [this message]
2004-11-04 0:15 ` 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=20041103223711.GG4249@tausq.org \
--to=randolph@tausq.org \
--cc=cagney@gnu.org \
--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