Wireshark-bugs: [Wireshark-bugs] [Bug 1416] crash (stack smashing) on single DHCP packet
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1416
------- Comment #5 from stephentfisher@xxxxxxxxx 2007-05-25 19:06 GMT -------
I'm unable to reproduce this on FreeBSD 6.1-REL and Fedora Core 6 Linux nor can
I get Valgrind to detect stack smashing.
However, I started looking at this bug the other day trying to figure out how
to solve it without reproducing it. Thanks for the gdb output. The line 1454
from frame #9 of the gdb output in the original bug report has now moved down
to 1468 in the latest SVN and is the statement "return consumed". Right after
that, some special stack smashing detection code from gcc/libc is triggered to
crash the program. Do you know what version of glibc do you have?
Could you run Wireshark from gdb and place a breakpoint right before it crashes
to print out the value of consumed. When I do this, consumed = 3 for the
packet you attached, which is an acceptable value for consumed and the
function's return value (both int). Your breakpoint can be set with "break
packet-bootp.c:1467" and remember to add the -o and other options to Wireshark
with the run command in gdb instead of on the gdb command line. Let us know if
you need any assistance in getting this set up.
BTW, Does tshark crash in the same way on this packet? (I would think it does)
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
