Re: [Wireshark-dev] code coverage measurement for a dissector?

2008-01-02 Thread Stig Bjørlykke
On 2. jan.. 2008, at 21.20, Németh Márton wrote: Bad news: the make process was not able to finish, here is the error: Did you make clean? It seems to work on my Ubuntu 7.10. -- Stig Bjørlykke ___ Wireshark-dev mailing list

Re: [Wireshark-dev] code coverage measurement for a dissector?

2008-01-02 Thread Stig Bjørlykke
On 3. jan.. 2008, at 00.19, Németh Márton wrote: I started with make distclean. What is your gcc version? gcc (GCC) 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2) It compiles ok, but I don't get any gcov output for the dissectors (which is in a lib). Maybe I'm doing it wrong... --

Re: [Wireshark-dev] code coverage measurement for a dissector?

2008-01-02 Thread Németh Márton
Stig Bjørlykke wrote: On 3. jan.. 2008, at 00.19, Németh Márton wrote: I started with make distclean. What is your gcc version? gcc (GCC) 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2) It compiles ok, but I don't get any gcov output for the dissectors (which is in a lib).

Re: [Wireshark-dev] code coverage measurement for a dissector?

2008-01-02 Thread Németh Márton
Stig Bjørlykke wrote: On 3. jan.. 2008, at 00.19, Németh Márton wrote: I started with make distclean. What is your gcc version? gcc (GCC) 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2) It compiles ok, but I don't get any gcov output for the dissectors (which is in a lib).

[Wireshark-dev] code coverage measurement for a dissector?

2008-01-01 Thread Németh Márton
Hi, 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? Will this work

Re: [Wireshark-dev] code coverage measurement for a dissector?

2008-01-01 Thread Stephen Fisher
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