1.6.6 isn't scheduled yet, but it's been a couple of months since 1.6.5
which would imply that it shouldn't be too much longer.
vijay wrote:
Is it possible to tell how longer would it be before Wireshark 1.6.6 is
released ?
On Mon, Mar 5, 2012 at 1:31 AM, Guy Harris g...@alum.mit.edu
Is it possible to tell how longer would it be before Wireshark 1.6.6 is
released ?
On Mon, Mar 5, 2012 at 1:31 AM, Guy Harris g...@alum.mit.edu wrote:
On Mar 4, 2012, at 8:24 PM, Jeff Morriss wrote:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5939
It's scheduled to be fixed in
I digged in bit further and found where the SIGSEV is signaled. Its coming
from the p_stats(). Here is what i got in gdb
[New Thread 0xb78acb70 (LWP 3668)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb78acb70 (LWP 3668)]
0x00f6f433 in pcap_stats () from
On Mar 4, 2012, at 2:23 AM, vijay wrote:
I digged in bit further and found where the SIGSEV is signaled. Its coming
from the p_stats(). Here is what i got in gdb
[New Thread 0xb78acb70 (LWP 3668)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb78acb70 (LWP
This is from dumpcap. Here is the complete stack. It occurring *while
writing the IDB*
#0 0x00ac7433 in pcap_stats () from /usr/lib/libpcap.so.0.8
#1 0x080513de in libpcap_write_interface_statistics_block (fp=0x805af70,
interface_id=0, pd=0x0, bytes_written=0x80572fc, err=0xbfffd2a8) at
On 03/04/2012 05:28 PM, vijay wrote:
This is from dumpcap. Here is the complete stack. It occurring *while
writing the IDB*
#0 0x00ac7433 in pcap_stats () from /usr/lib/libpcap.so.0.8
#1 0x080513de in libpcap_write_interface_statistics_block
(fp=0x805af70, interface_id=0, pd=0x0,
On Mar 4, 2012, at 8:24 PM, Jeff Morriss wrote:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5939
It's scheduled to be fixed in 1.6.6.
...and I backported the relevant part (a tiny fraction of the change
responsible for fixing it in the trunk; that change added a bunch of new
