From: Jason Kraftcheck <kraftche@cae.wisc.edu>
To: gdb-patches@sources.redhat.com
Subject: list/edit command on frame with available symtab
Date: Thu, 23 Feb 2006 18:45:00 -0000 [thread overview]
Message-ID: <43FE018B.2050502@cae.wisc.edu> (raw)
If there is no symtab for the current frame, traverse up the stack
looking for a frame with a symtab. This may at first seem like a
gratuitous feature (and perhaps it is), but I find it is convenient when
working with an application that uses third-party libraries. Typically
whatever code I'm working on has debug symbols while whatever
third-party code I'm calling does not. And I'm much more interested in
seeing where the process was in my code at the time a fault occurred. I
don't think this change will be a problem for anyone, as the previous
behavior was to print an error if there was no symtab.
2006-02-23 Jason Kraftcheck <kraftche@cae.wisc.edu>
* stack.c (set_current_sal_from_frame): If list or edit command
is invoked for a frame without a symtab, move up the stack to
the neareast frame with a symtab.
diff -upr gdb-6.4/gdb/stack.c mod/gdb/stack.c
--- gdb-6.4/gdb/stack.c 2005-08-18 08:26:41.000000000 -0500
+++ mod/gdb/stack.c 2006-02-23 11:55:12.481291546 -0600
@@ -377,8 +377,18 @@ static void
set_current_sal_from_frame (struct frame_info *frame, int center)
{
struct symtab_and_line sal;
+ int count;
find_frame_sal (frame, &sal);
+ while (!sal.symtab)
+ {
+ count = 1;
+ frame = find_relative_frame( frame, &count );
+ if (count)
+ break;
+ find_frame_sal (frame, &sal);
+ }
+
if (sal.symtab)
{
if (center)
next reply other threads:[~2006-02-23 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 18:45 Jason Kraftcheck [this message]
2006-02-23 21:02 ` Daniel Jacobowitz
2006-02-23 22:13 ` Jason Kraftcheck
2006-03-01 22:35 ` Michael Snyder
2006-03-30 16:26 ` Daniel Jacobowitz
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=43FE018B.2050502@cae.wisc.edu \
--to=kraftche@cae.wisc.edu \
--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