Bug 7143 - Feature request: Readability of backtraces
Summary: Feature request: Readability of backtraces
Status: RESOLVED INVALID
Alias: None
Product: Samba 4.0
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: Other Linux
: P3 enhancement (vote)
Target Milestone: ---
Assignee: Andrew Bartlett
QA Contact: samba4-qa@samba.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-16 21:34 UTC by John H Terpstra (mail address dead(
Modified: 2012-10-25 08:37 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John H Terpstra (mail address dead( 2010-02-16 21:34:17 UTC 
You can also file a bug for the fact that the backtraces are so hard to read
(with %s stuff in the exception). 

Then, 'wbclient -u' - which failed to connect.  The error log show:

[Mon Feb 15 23:06:07 2010 CST, 0 nbt_server/irpc.c:125:nbtd_getdcname()]
nbtd_getdcname called
[Mon Feb 15 23:06:07 2010 CST, 0
librpc/rpc/dcerpc_util.c:625:dcerpc_pipe_auth_recv()]
Failed to bind to uuid 12345678-1234-abcd-ef00-01234567cffb -
NT_STATUS_UNSUCCESSFUL
[Mon Feb 15 23:06:07 2010 CST, 0
lib/cmdline/popt_common.c:58:popt_s4_talloc_log_fn()]
talloc: double free error - first free may be at
winbind/wb_samba3_protocol.c:316
[Mon Feb 15 23:06:07 2010 CST, 0
lib/cmdline/popt_common.c:58:popt_s4_talloc_log_fn()]
Bad talloc magic value - double free
[Mon Feb 15 23:06:07 2010 CST, 0 ../lib/util/fault.c:143:smb_panic()]
PANIC: Bad talloc magic value - double free
[Mon Feb 15 23:06:07 2010 CST, 0 ../lib/util/fault.c:62:call_backtrace()]
BACKTRACE: 33 stack frames:
 #0 samba(call_backtrace+0x1f) [0xe3710b]
 #1 samba(smb_panic+0x212) [0xe373d5]
 #2 samba [0xe519cd]
 #3 samba [0xe51a49]
 #4 samba [0xe51ac6]
 #5 samba [0xe51d25]
 #6 samba(talloc_vasprintf+0x7f) [0xe545d7]
 #7 samba(talloc_asprintf+0xcc) [0xe5471a]
 #8 samba [0x6f4919]
 #9 samba(_tevent_req_notify_callback+0x38) [0xe58be1]
 #10 samba [0xe58c13]
 #11 samba(_tevent_req_done+0x25) [0xe58c3a]
 #12 samba [0x803b03]
 #13 samba(_tevent_req_notify_callback+0x38) [0xe58be1]
 #14 samba [0xe58c13]
 #15 samba(_tevent_req_done+0x25) [0xe58c3a]
 #16 samba [0xb6c23d]
 #17 samba(_tevent_req_notify_callback+0x38) [0xe58be1]
 #18 samba [0xe58c13]
 #19 samba [0xe58d0c]
 #20 samba(tevent_common_loop_immediate+0x1f9) [0xe57804]
 #21 samba [0xe5a6c9]
 #22 samba(_tevent_loop_once+0xe8) [0xe55e94]
 #23 samba(tevent_common_loop_wait+0x25) [0xe560d1]
 #24 samba(_tevent_loop_wait+0x2b) [0xe5619c]
Comment 1 Andrew Bartlett 2010-02-16 21:47:42 UTC 
I actually meant the python backtraces from the exceptions in provision, but anyway...
Comment 2 Matthias Dieter Wallnöfer 2010-02-17 12:31:26 UTC 
Marking as "feature request"
Comment 3 Stefan Metzmacher 2012-10-25 08:32:07 UTC 
If someone needs better backtraces, build with debug info
and use the gdb_backtrace script as panic action.

I don't see how we can improve anything from within samba.
Comment 4 Andrew Bartlett 2012-10-25 08:37:36 UTC 
we could change the default panic action to gdb_backtrace, perhaps only for --enable-developer and --enable-debug builds.