Wireshark-bugs: [Wireshark-bugs] [Bug 2630] rtp_player crashes on decode of long call: BadAlloc
Tirian Wilson
changed
bug 2630
| What |
Removed |
Added |
| CC |
|
twilson@liberty.edu
|
Comment # 13
on bug 2630
from Tirian Wilson
I am running CentOS 6.3 and think I am hitting this bug. In the past, I used
the version of Wireshark in the EPEL repo but it is version 1.2. Now I need
some features that are in 1.8 so I downloaded the source from wireshark.org and
used the .spec file to create a RPM. Then I uninstalled all Wireshark packages
and installed the RPM created from the Wireshark provided .spec file. However,
now when I try to work with calls longer than a couple of minutes, it crashes.
Here is an example capture file that shows the issue along with a crashdump
from Wireshark. The specific call is to 504-655-6855 and starts at 17:46:19.
Here is a link to the example capture and core dump:
https://docs.google.com/file/d/0B-38kgnrbT74OTZyZlphOGxSeUU/edit
This is the console log from the crash:
[tirian@rhyme caps]$ ulimit -c unlimited
[tirian@rhyme caps]$ wireshark
Xlib: extension "RANDR" missing on display ":0.0".
Gdk-ERROR **: The program 'wireshark' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 118653 error_code 11 request_code 53 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...
Aborted (core dumped)
[tirian@rhyme caps]$
You are receiving this mail because:
- You are the assignee for the bug.
- You are watching all bug changes.
