Changes between Initial Version and Version 4 of Ticket #13480
- Timestamp:
- Jan 16, 2008, 4:48:56 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #13480
-
Property
Status
changed from
new
toclosed
-
Property
Resolution
changed from
to
duplicate
-
Property
Milestone
changed from
Port Bugs
to
-
Property
Status
changed from
-
Ticket #13480 – Description
initial v4 1 1 When I run Wireshark, and I try to open an existing capture file, wireshark crashes when I click on the "OK" button in the Open dialog. This is written out to the shell where I started it: 2 2 3 {{{ 3 4 smitty@Smittys-MacBook-Pro ~$ sudo wireshark 4 5 The program 'wireshark' received an X Window System error. … … 11 12 option to change this behavior. You can then get a meaningful 12 13 backtrace from your debugger if you break on the gdk_x_error() function.) 14 }}} 13 15 14 16 Unfortunately, trying to run it in gdb didn't seem to help me figure out the underlying cause. I don't know how to look up X Window System error codes. I also remember it crashing when I would be doing a capture … … 16 18 Interestingly, if I run wireshark like this: 17 19 20 {{{ 18 21 $ sudo wireshark -r mySampleFile 22 }}} 19 23 20 24 it opens up the file just fine. So the problem is likely in something outside wireshark (dependent library). … … 22 26 Similarly, if I run wireshark and start a capture, it will capture packets just fine. But when the number of captured packets is longer than what can be presented in the window, and would force the user to use the scrollbar to see the bottom, it crashes. I can make it crash earlier by making the window smaller (quiet network at home allows me to recognize this). The dumps to my terminal window when it does that seems to vary: 23 27 28 {{{ 24 29 smitty@Smittys-MacBook-Pro ~$ sudo wireshark 25 30 Password: … … 65 70 backtrace from your debugger if you break on the gdk_x_error() function.) 66 71 smitty@Smittys-MacBook-Pro ~$ 67 72 }}}