http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1025
------- Comment #5 from jmayer@xxxxxxxxx 2006-08-10 04:15 GMT -------
More analysis from Neil Piercy:
The crash only happens trying to display the response packets in the bug
trace - handling the request packets is fine, and both go through the
same execution path in this area. The big difference between the request
and the response is that the _values_ of the 64 bit monotonic replay
detection counter: the requests use very small values, the responses use
huge values (i.e. all bytes of the 64 bit values are non-zero).
The crash definitely happens deep in the glib handling of the
g_vsnprintf - I dont have a debug build of glib, but it looked like it
went into the guts of the core gnulib/vasnprintf, where it hit an abort
call. Without the debug lib it is difficult to see where or why.
Bottom line: looks to me like a glib bug or a build incompatibility
between guint64 handling in the glib binary and ethereal perhaps?
--
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.
