Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 2675] New: segmentation fault when loading trace

[bugzilla-daemon@xxxxxxxxxxxxx]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2675

           Summary: segmentation fault when loading trace
           Product: Wireshark
           Version: 1.0.1
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Medium
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: thnielsen@xxxxxxxxxx


Build Information:
Version 1.0.1

Copyright 1998-2008 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled with GTK+ 2.13.3, with GLib 2.17.2, with libpcap 0.9.8, with libz
1.2.3, without POSIX capabilities, with libpcre 7.6, without SMI, without ADNS,
without Lua, without GnuTLS, without Gcrypt, without Kerberos, without
PortAudio, without AirPcap.

Running on Linux 2.6.25.9-2-pae, with libpcap version 0.9.8.

Built using gcc 4.3.2 20080613 (prerelease) [gcc-4_3-branch revision 136744].


Also tested:

wireshark 1.0.0

Copyright 1998-2008 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled with GTK+ 2.13.3, with GLib 2.17.2, with libpcap 0.9.8, with libz
1.2.3, without POSIX capabilities, with libpcre 7.6, without SMI, with ADNS,
without Lua, without GnuTLS, without Gcrypt, with MIT Kerberos, without
PortAudio, without AirPcap.

Running on Linux 2.6.25.9-2-pae, with libpcap version 0.9.8.

Built using gcc 4.3.2 20080613 (prerelease) [gcc-4_3-branch revision 136744].
--
Good afternoon
I have had this so often, that i decided to make an effort to file a meaning
full bugreport.
I often get traces from a customer, and they often crash wireshark when
loading. I have tried the 2 different version above, but also on other machines
it fails - think it is systematic. in my opinion wireshark should not seg
fault, but rather exit with a meaning full message if it does no like a trace
:-)
I can provide a sample trace on request - it will load until about 9 percent
and the seg fault wireshark.
I prefer to email the location of the trace for customer discretion.


to reproduce on my trace:
launch
./wireshark  /tmp/tracefile 
and you will get:
Segmentation fault


-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.