Ask Your Question
0

Source files changed after build

asked 2019-05-08 12:54:30 +0000

CarloT gravatar image

Hello, is it ok, that after the build process some of the source files have been changed and some other has been added?

Here there are some of the files that has been changed after build:: - Wireshark\epan\dfilter\grammar.c - Wireshark\epan\dfilter\scanner.c - wireshark\epan\diam_dict.c - wireshark\epan\dtd_grammar.c - wireshark\epan\dtd_parse.c - wireshark\epan\dtd_preparse.c - wireshark\epan\radius_dict.c - wireshark\epan\uat_load.c - etc

And here there are some of the files that has been generated after build: - wireshark\epan\inet_ntap.c - wireshark\epan\inet_ptap.c - wireshark\epan\mkstenp.c - wireshark\epan\strptime.c - wireshark\svnversion.h - wireshark\config.h

I am using Wireshark 0.99.7.

Thank you, Carlo

edit retag flag offensive close merge delete

1 Answer

Sort by » oldest newest most voted
0

answered 2019-05-08 15:17:37 +0000

grahamb gravatar image

That version has been EOL'd for a very long time, so support will be mostly non-existent.

Are you building from a tarball, if so then it may include some generated files that get regenerated during the build?

Out of interest, why are you compiling such an old version?

edit flag offensive delete link more

Comments

Hello, and thank you!

Yes I am building from a tarball.
Reading your answer I get that it may include some generated files. So it is normal that these files can be regenerated during build, and some other can be generated from scratch.

My anxiety comes form the high number of differencies that I see, when I compare some of these files. For example. try to compare theese two files:
- diam_dict.c - https://drive.google.com/open?id=1E_q...
- diam_dict.rebuilt.c - https://drive.google.com/open?id=18v7...

Is it normal? Can I sleep pacefully? ;)

I am using Wireshark 0.99.7, because some years ago I have developed an ehercat voe dissector on that Wireshark version, that now I need to update in a very short time…

Thank you, Carlo

CarloT gravatar imageCarloT ( 2019-05-09 07:12:02 +0000 )edit

As nobody else is building that version now, we're relying on ancient memories, but I would expect everything is OK. The build from that version is what it is, so unless you've managed to obtain a trojan'ed tarball, I wouldn't worry about it.

grahamb gravatar imagegrahamb ( 2019-05-09 09:54:12 +0000 )edit

I have done some regression test, respect Wireshark 0.99.7 + old dissector (buid with XP and VS2003).

I haven't seen differencies, using the regenerated Wireshark + regenerated dissector (build with W10 and VS2005). I have seen differencies, instead, using Wireshark 0.99.7 + regenerated dissector.

The dissector sources are the same. They have only been rebuilt with VS2005, instead of VS2003. Why I have this different behaviour?

CarloT gravatar imageCarloT ( 2019-05-09 12:24:11 +0000 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2019-05-08 12:54:30 +0000

Seen: 34 times

Last updated: May 08