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-dev: Re: [Wireshark-dev] code coverage measurement for a dissector?

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


From: Stephen Fisher <stephentfisher@xxxxxxxxx>
Date: Tue, 1 Jan 2008 17:01:51 -0700

On Tue, Jan 01, 2008 at 11:37:30PM +0100, Németh Márton wrote:

> I would like to write some tests for my dissector. To check how far I 
> could cover my dissector code I could use the "--coverage" option of 
> the gcc (see 
> http://gcc.gnu.org/onlinedocs/gcc/Debugging-Options.html#index-coverage-375 
> ).
> 
> Where do I have to put the "--coverage" option?

Set the environment variable CFLAGS to "--coverage" and re-run the 
configure script then rebuild Wireshark with make (see ./configure 
--help for more details).

> Will this work together with Wireshark?

Not sure - this is the first I have heard of that gcc option.  Try it 
out and let us know how it went.


Steve

  • Follow-Ups:
    • Re: [Wireshark-dev] code coverage measurement for a dissector?
      • From: Németh Márton
  • References:
    • [Wireshark-dev] code coverage measurement for a dissector?
      • From: Németh Márton
  • Prev by Date: [Wireshark-dev] code coverage measurement for a dissector?
  • Next by Date: Re: [Wireshark-dev] code coverage measurement for a dissector?
  • Previous by thread: [Wireshark-dev] code coverage measurement for a dissector?
  • Next by thread: Re: [Wireshark-dev] code coverage measurement for a dissector?
  • Index(es):
    • Date
    • Thread

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