Wireshark-bugs: [Wireshark-bugs] [Bug 7579] Segmentation fault on dumpcap -D

Date: Mon, 6 Aug 2012 13:34:53 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7579

Guy Harris <guy@xxxxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #7 from Guy Harris <guy@xxxxxxxxxxxx> 2012-08-06 13:34:52 PDT ---
> Same thing append with tcpdump :

That means it's almost certainly a libpcap bug, not a tcpdump or Wireshark bug.

> Program received signal SIGSEGV, Segmentation fault.
> 0xb7d5e13f in __opendirat () from /lib/libc.so.6
> (gdb) bt
> #0  0xb7d5e13f in __opendirat () from /lib/libc.so.6
> #1  0xb7d5e1bd in opendir () from /lib/libc.so.6
> #2  0xb7c330fe in ?? () from /lib/libusb-1.0.so.0
> #3  0xb7c2aca8 in libusb_get_device_list () from /lib/libusb-1.0.so.0
> #4  0xb7e9c91b in canusb_platform_finddevs () from /lib/libpcap.so.1
> #5  0xb7e98f87 in pcap_platform_finddevs () from /lib/libpcap.so.1
> #6  0xb7e9cd32 in pcap_findalldevs () from /lib/libpcap.so.1
> #7  0x0804dceb in get_interface_list_findalldevs ()
> #8  0x0804d8ec in capture_opts_trim_iface ()
> #9  0x0804ba64 in main ()

That is the following libpcap bug:

   
http://sourceforge.net/tracker/?func=detail&atid=469577&aid=3554749&group_id=53067

That bug says:

> Running tcpdump on a host without a mounted usbfs will result in a segfault, unless the interface is specified.
> 
> The return value of libusb_init() [1] should be checked to make sure it's appropriate to continue with the other calls to libusb.

and the reported stack trace:

    http://pastie.org/4392531

is, starting with pcap_findalldevs(), the same.

I.e., it's a libpcap bug, not a Wireshark bug.  Closing.  I'll fix the libpcap
bug when I get the chance; I'll ask Michael Richardson to put out a libpcap
1.3.1 release, for various upstream Linux distributions to pick up (or they can
just pick it up themselves from Git).  ("INVALID" should really be, as a
certain purple-anteater-themed bug system would call it, "3rd party to
resolve", the "3rd party" here being tcpdump.org, but there's no such
resolution in the Wireshark Bugzilla.  I think some other Bugzillas may have
that.)

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