Am 20.11.2010 08:42, schrieb Andreas:
> Where can I get the .PDB files for the Wireshark binaries? They are
> created in the wireshark-gtk2 directory when you (successfully) compile
> the sources. I am interested in the libwireshark.pdb and wireshark.pdb
> of a recent version, i.e. 1.4.1, 1.4.2 and/or 1.2.13.
>
> Background:
> When debugging my own dissectors it's sometimes useful to trace into the
> epan functions, what requires these debug program database.

I tried to compile the wireshark sources to generate libraries and PDBs. 
After "nmake -f Makefile.name setup" I started the build process. This 
fails always with this message:

----<>-----<>-----<>-----<>-----<>-----<>-----<>-----<>-----<>-----
a...@falke /cygdrive/c/wireshark-1.4.1
$ nmake -f Makefile.nmake epan

Microsoft (R) Program Maintenance Utility Version 9.00.21022.08
Copyright (C) Microsoft Corporation.  All rights reserved.

         cd image
         "C:\Program Files (x86)\Microsoft Visual Studio 
9.0\VC\BIN\nmake.exe" /                   -f Makefile.nmake

Microsoft (R) Program Maintenance Utility Version 9.00.21022.08
Copyright (C) Microsoft Corporation.  All rights reserved.

         cd ..
         cd wiretap
         "C:\Program Files (x86)\Microsoft Visual Studio 
9.0\VC\BIN\nmake.exe" /                   -f Makefile.nmake

Microsoft (R) Program Maintenance Utility Version 9.00.21022.08
Copyright (C) Microsoft Corporation.  All rights reserved.

         bison  -d -p ascend ascend.y -o ascend.c
/usr/bin/bison: m4 subprocess failed
NMAKE : fatal error U1077: 'C:\Cygwin\bin\bison.EXE' : return code '0x1'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual 
Studio 9.0\VC\BIN\nmake.exe"' : return code '0x2'
Stop.
----<>-----<>-----<>-----<>-----<>-----<>-----<>-----<>-----<>-----

What may be wrong here?


BTW: Despite the developer guide did not mentioned it, it was necessary 
to install sed in cygwin. I also renamed the /bin/link.exe so that the 
VS2008 linker could be found.


Andy

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Reply via email to