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: Guy Harris <guy@xxxxxxxxxxxx>
Date: Mon, 11 Feb 2008 01:38:03 -0800

Stephen RP O'Connell wrote:
It prints:

gencode.c:      (void)pcap_parse();
gencode.h:int pcap_parse(void);
grammar.c:pcap_parse()
grammar.y:pcap_parse()

What does

	nm -po /usr/local/lib/libpcap.a | egrep pcap_parse

print?

(I'm assuming this is Linux; if it's not, you might as well give up, unless you're writing your own USB support or got the USB support from somebody else, as the current CVS version of libpcap supports only Linux.)

  • Follow-Ups:
    • Re: [Wireshark-users] Compilation problems with CVS libpcap
      • From: Stephen RP O'Connell
  • 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
  • Prev by Date: Re: [Wireshark-users] Bad Checksum Packet
  • Next by Date: Re: [Wireshark-users] Compilation problems with CVS libpcap
  • 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