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: Tue, 12 Feb 2008 09:07:47 +0000

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?

Quoting Guy Harris <guy@xxxxxxxxxxxx>:

> Stephen RP O'Connell wrote:
> 
> > YACC = bison -y -p pcap_
> 
> Well, that's what it's supposed to be, and that's supposed to cause the 
> generated grammar.c to define its functions with names beginning with 
> pcap_, not yy.
> 
> What happens if you go to the source directory for libpcap, do "make 
> clean", do "make", and then do "nm -po libpcap.a | egrep parse"?
> _______________________________________________
> Wireshark-users mailing list
> Wireshark-users@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-users
> 





  • Follow-Ups:
    • Re: [Wireshark-users] Compilation problems with CVS libpcap
      • From: Guy Harris
  • 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
  • Prev by Date: Re: [Wireshark-users] How to let wireshark capture one application packets
  • Next by Date: [Wireshark-users] where to see transfered data
  • Previous by thread: Re: [Wireshark-users] Compilation problems with CVS libpcap
  • Next by thread: Re: [Wireshark-users] Compilation problems with CVS libpcap
  • Index(es):
    • Date
    • Thread

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