This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug python/16486] New: differences between "bt" and "bt no-filters"
- From: "tromey at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 22 Jan 2014 06:56:42 +0000
- Subject: [Bug python/16486] New: differences between "bt" and "bt no-filters"
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=16486
Bug ID: 16486
Summary: differences between "bt" and "bt no-filters"
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: python
Assignee: unassigned at sourceware dot org
Reporter: tromey at redhat dot com
While working on a frame filter I noticed some output differences
between "bt" and "bt no-filters". I think that if there is
a "null" filter (that just passes through the FrameDecorator objects),
then there should, ideally, be no differences between the two
cases.
Here's a frame from "bt":
#0 0x0000000000402f10 in on_generic_marshaller_1 (obj=0x615500 [Test],
v_schar=42 '*', v_uchar=43 '+', v_int=4096, v_long=8192, v_pointer=0x0,
v_double=0.5, v_float=5.5, user_data=0x0) at signals.c:400
The same frame from "bt no-filters":
#0 on_generic_marshaller_1 (obj=0x615500 [Test], v_schar=42 '*',
v_uchar=43 '+', v_int=4096, v_long=8192, v_pointer=0x0, v_double=0.5,
v_float=5.5, user_data=0x0) at signals.c:400
It may not be totally obvious here; but if you construct a test case
and make your terminal very large, you can see that the filtering
code prints the entire frame as a single long line.
The no-filter code still wraps; perhaps this is a separate bug (since
the screen size changed I would assume gdb would notice); but in any
case the wrapping and indentation looks nicer.
--
You are receiving this mail because:
You are on the CC list for the bug.