This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

how to generate dsp file in VS2008EE by Wireshark’s source codes?

0

i want to debug the Wireshark's source codes in VS2008EE, but there are only makefile, not dsp file.

how to generate dsp file in VS2008EE by Wireshark's source codes?

asked 14 Sep '11, 01:59

ylda_ljm0620's gravatar image

ylda_ljm0620
31101013
accept rate: 0%

edited 14 Sep '11, 12:31

Bill%20Meier's gravatar image

Bill Meier ♦♦
3.2k1850


2 Answers:

1

To debug Wireshark on Windows:

  1. Build Wireshark on Windows from the commandline using the Wireshark nmakefile with VS2008EE in the normal manner (as described in the Developers Guide).

  2. Start the VC2008EE GUI.

  3. Do File ! Open ! Project/Solution on wireshark-gtk2\wireshark.exe

You'll be able to do debugging of Wireshark in the normal manner with source code viewing, breakpoints & etc.

answered 14 Sep '11, 12:06

Bill%20Meier's gravatar image

Bill Meier ♦♦
3.2k1850
accept rate: 17%

edited 14 Sep '11, 12:28

0

Wireshark is normally built using nmake and a Makefile, not a Visual Studio project. There is an alternative CMake build system for Wireshark but I've not had much success with it on Windows and using Visual Studio Express compilers. I think CMake can be persuaded to output Visual Studio project files but I've never done that.

To debug on Windows your options are:

Use WinDbg. Downloadable from MS, works well but has a bit of a learning curve, but for simple debugging is sufficient. Use a more full featured version of Visual Studio, i.e. Pro or above and use the debugger command to "Attach To Process". Using CMake or by hand create a project file for Wireshark to use in Visual Studio Express.

answered 14 Sep '11, 04:19

grahamb's gravatar image

grahamb ♦
19.8k330206
accept rate: 22%

Visual Studio 2008 EE will do Attach to Process. There is no need to upgrade to pro for this functionality.

(14 Sep '11, 05:22) multipleinte...

Ah, VS 2010 EE doesn't have that in the debug menu so I assumed it was the same for VS 2008.

(14 Sep '11, 13:32) grahamb ♦