This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug python/16486] differences between "bt" and "bt no-filters"
- From: "pmuldoon at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 21 Feb 2014 12:55:00 +0000
- Subject: [Bug python/16486] differences between "bt" and "bt no-filters"
- Auto-submitted: auto-generated
- References: <bug-16486-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16486
Phil Muldoon <pmuldoon at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pmuldoon at redhat dot com
--- Comment #1 from Phil Muldoon <pmuldoon at redhat dot com> ---
I've added the missing wrap hints in the same places as the "no-filter" option.
I will submit that soon. However, I also noticed that for the first frame,
the "no-filter" option does not print an address, but the frame filtered
version does.
I looked into this, and if the sal.pc == current_frame.pc then the address is
not printed.
(This is the line in GDB)
Breakpoint 2, frame_show_address (frame=0x101ad50, sal=...) at
../../binutils-gdb/gdb/stack.c:146
146 return get_frame_pc (frame) != sal.pc;
I thought about fixing this, but I think it is somewhat of an arbitrary
decision for GDB to make over the frame filters. After all, each frame filter
can either choose to show whatever address on whatever line it chooses.
So I decided not to fix that. What do you think?
--
You are receiving this mail because:
You are on the CC list for the bug.