Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-users: Re: [Wireshark-users] Compilation problems with CVS libpcap

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: "Stephen RP O'Connell" <srpoc103@xxxxxxxxxxxxxxx>
Date: Wed, 13 Feb 2008 10:07:01 +0000

I've just tried compiling the current SVN version but I still get the same
error. There isn't any isochronous traffic on the bus I'm looking at at the
moment, it's all control and interrupt URBs. 

The message box I get when Wireshark stops checking for URBs is

Error while capturing packets: Can't parse urb tag from '
'

with the following error in the main Wireshark window:

[Dissector bug, protocol USB: packet-usb.c:1013: failed assertion
"DISSECTOR_ASSERT_NOT_REACHED"]

The message box says to report the bug to the developers - is this the next step?

Quoting Guy Harris <guy@xxxxxxxxxxxx>:

> Stephen RP O'Connell wrote:
> > That's sorted it, thanks very much for all of your help :) I've now got
> > Wireshark compiled with libpcap 0.9-PRE-CVS, however when I try and
> capture
> > any USB packets I get the following error:
> > 
> > [Dissector bug, protocol USB: packet-usb.c:1004: failed assertion
> > "DISSECTOR_ASSERT_NOT_REACHED"]
> > 
> > Has anyone seen this before?
> 
> Márton Németh did, apparently; a change was checked into the USB 
> dissector after 0.99.7 was released, with the comment:
> 
> 	From Márton Németh:
> 	When an ISOCHRONOUS URB was captured the packet-usb.c does not handle it.
> 	Case URB_ISOCHRONOUS was added at two different places to handle it also.
> 
> so you probably are getting isochronous traffic, and the dissector isn't 
> handling it.
> 
> You might try compiling the current SVN version and using that.  (It 
> requires more tools to be installed than does compiling a release tarball:
> 
> 	http://www.wireshark.org/develop.html
> 
> See, for example, the Developer's Guide, linked to from there.
> _______________________________________________
> Wireshark-users mailing list
> Wireshark-users@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-users
> 





  • References:
    • [Wireshark-users] Compilation problems with CVS libpcap
      • From: Stephen O'Connell
    • Re: [Wireshark-users] Compilation problems with CVS libpcap
      • From: Guy Harris
    • Re: [Wireshark-users] Compilation problems with CVS libpcap
      • From: Stephen RP O'Connell
    • Re: [Wireshark-users] Compilation problems with CVS libpcap
      • From: Guy Harris
    • Re: [Wireshark-users] Compilation problems with CVS libpcap
      • From: Stephen RP O'Connell
    • Re: [Wireshark-users] Compilation problems with CVS libpcap
      • From: Guy Harris
    • Re: [Wireshark-users] Compilation problems with CVS libpcap
      • From: Stephen RP O'Connell
    • Re: [Wireshark-users] Compilation problems with CVS libpcap
      • From: Guy Harris
    • Re: [Wireshark-users] Compilation problems with CVS libpcap
      • From: Stephen RP O'Connell
    • Re: [Wireshark-users] Compilation problems with CVS libpcap
      • From: Guy Harris
    • Re: [Wireshark-users] Compilation problems with CVS libpcap
      • From: Stephen RP O'Connell
    • Re: [Wireshark-users] Compilation problems with CVS libpcap
      • From: Guy Harris
  • Prev by Date: Re: [Wireshark-users] Wireshark sold on ebay
  • Next by Date: Re: [Wireshark-users] Network disconnects
  • Previous by thread: Re: [Wireshark-users] Compilation problems with CVS libpcap
  • Next by thread: [Wireshark-users] Which hardware
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation