|
From: Steve F. <sf...@re...> - 2003-08-06 17:31:40
|
Greg Hudson wrote: >After rooting through the valgrind source, I discovered that I am >blind, and the address info I coveted is displayed between two partial >stack traces: > >==6579== Syscall param writev(vector[...]) contains uninitialised or unaddressable byte(s) >==6579== at 0x40181C24: vgAllRoadsLeadToRome_writev (vg_intercept.c:108) >==6579== by 0x40181C60: __writev (vg_intercept.c:732) >==6579== by 0x407C311D: (within /usr/lib/liblinc.so.1.0.0) >==6579== by 0x407C32AB: linc_connection_writev (in /usr/lib/liblinc.so.1.0.0) >==6579== Address 0x4402E83E is 10 bytes inside a block of size 2048 alloc'd >==6579== at 0x4002942A: malloc (vg_replace_malloc.c:153) >==6579== by 0x4112F558: g_malloc (in /usr/lib/libglib-2.0.so.0.200.1) >==6579== by 0x4078531E: get_next_indirect (giop-send-buffer.c:273) >==6579== by 0x407853E3: giop_send_buffer_append_copy (giop-send-buffer.c:295) > >I think I would have been less likely to have missed it if the >"Address 0x4402E83E" line weren't indented. Here's a trivial patch to >de-indent address-info headers if the powers that be agree with me. > As a representative of the Powerless That Be, I would rather not see this patch applied as-is. It's already too difficult to scan past the fault records. On the other hand, I also agree with your complaint. Perhaps a half-indent? A special character in the first column? With respect to making fault records easier to scan past, I'd love to see either a newline after a fault record (so you can skip past paragraphs in the editor of your choice), or some fixed searchable text at the beginning of each record. |