Bug 639691 - [abrt] wireshark-gnome-1.2.10-1.fc13: col_append_fstr: Process /usr/sbin/wireshark was killed by signal 11 (SIGSEGV)
Summary: [abrt] wireshark-gnome-1.2.10-1.fc13: col_append_fstr: Process /usr/sbin/wire...
Keywords:
Status: CLOSED DUPLICATE of bug 632539
Alias: None
Product: Fedora
Classification: Fedora
Component: wireshark
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Radek Vokál
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:99cb292af44e0a69503b06d29d3...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-03 12:08 UTC by Tom Hughes
Modified: 2010-10-05 10:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-05 10:58:08 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (39.87 KB, text/plain)
2010-10-03 12:08 UTC, Tom Hughes 		no flags Details
Packet capture to demonstrate problem (1.15 KB, application/octet-stream)
2010-10-05 08:46 UTC, Tom Hughes 		no flags Details
View All

Description Tom Hughes 2010-10-03 12:08:52 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: wireshark -r /tmp/log
component: wireshark
crash_function: col_append_fstr
executable: /usr/sbin/wireshark
kernel: 2.6.34.6-47.fc13.x86_64
package: wireshark-gnome-1.2.10-1.fc13
rating: 4
reason: Process /usr/sbin/wireshark was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1286107350
uid: 500

How to reproduce
-----
Any time I click on a memcache packet to display the contents wireshark crashes with this trace.
Comment 1 Tom Hughes 2010-10-03 12:08:55 UTC 
Created attachment 451264 [details]
File: backtrace
Comment 2 Tom Hughes 2010-10-03 12:12:46 UTC 
This only seems to happen if the memcache packet is using the binary protocol rather than the ASCII protocol.
Comment 3 Jan Safranek 2010-10-05 08:38:17 UTC 
Please attach some captured packets which cause the crash. It would help me a lot to reproduce and fix the problem. Thanks in advance.
Comment 4 Tom Hughes 2010-10-05 08:46:16 UTC 
Created attachment 451606 [details]
Packet capture to demonstrate problem

Here's a pcap file that demonstrates the problem - just click on any of the memcache packets to make it crash.
Comment 5 Jan Safranek 2010-10-05 10:58:08 UTC 
Thanks for the report! I've fixed it recently, update was released just today :).

*** This bug has been marked as a duplicate of bug 632539 ***
Note You need to log in before you can comment on or make changes to this bug.