I finally found what was wrong. The GOOSE dissector is unsing "#line" instruction in its sources. Visual Studio does not seem to like that.
Nic Nicolas Gendron ing. jr (418) 834-0009 poste 266 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bill Meier Sent: September 23, 2009 4:54 PM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] I followed "Using MSVC++ for debugging" and still unable to debug Wireshark. Nicolas Gendron wrote: > On Windows XO, here is what I'm doing : > - make sure "config.nmake" is OK. I actually have "LOCAL_LDFLAGS=/DEBUG /MACHINE:$(TARGET_MACHINE)" uncommented > - make disclean > - make all > - start Visual Studio 2008 (Team System Development Edition) > - open Wireshark.exe > - try to put a breakpoint in "epan\packet-goose.c" > - start the debugging > > > My breakpoint becomes disabled because "no symbols have been loaded for this document" > Things should work just fine ... So: (starting with some basic random questions): 1. Did you open Wireshark in VS via File ! Open ! Project Solution ...\wireshark-gtk2\wireshark.exe ?? 2. If so: Can you "step in" (F11) to Wireshark and get a display of lots of "Loading symbols ..." in the bottom status VS bar before eventually getting a display of gtk/main.c source ?? ________________________________________________________________________ ___ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
