Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: Re: [Wireshark-dev] tshark (Windows) not working

From: "Maynard, Chris" <Christopher.Maynard@xxxxxxxxx>
Date: Mon, 10 May 2010 13:04:45 -0400

Currently I am unable to even get that far.  I’m at SVN32735 on Windows XP SP3 (32-bit) with cygwin 1.7.5(0.225/5/3), and after a “distclean”, compiling with VS2008EE fails due to a zlib-related manifest error.  Here’s the relevant output:

 

Microsoft (R) Program Maintenance Utility Version 9.00.30729.01

Copyright (C) Microsoft Corporation.  All rights reserved.

 

'zlib1.dll' is up-to-date

        if not exist C:\wireshark-win32-libs\zlib123 mkdir C:\wireshark-win32-libs\zlib123

        if not exist C:\wireshark-win32-libs\zlib123\lib mkdir C:\wireshark-win32-libs\zlib123\lib

        if not exist C:\wireshark-win32-libs\zlib123\include mkdir C:\wireshark-win32-libs\zlib123\include

        mt.exe -nologo -manifest "zlib1.dll.manifest" -outputresource:zlib1.dll;2

 

zlib1.dll.manifest : general error c1010070: Failed to load and parse the manifest. The system cannot find the file specified.

NMAKE : fatal error U1077: '"C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin\mt.exe"' : return code '0x1f'

Stop.

 

In case it was due to the SDK, I tried to update it to the latest from here:

http://www.microsoft.com/downloads/details.aspx?FamilyID=c17ba869-9671-4330-a63e-1fd44e0e2505&displaylang=en

 

… but no luck:

 

Microsoft (R) Program Maintenance Utility Version 9.00.30729.01

Copyright (C) Microsoft Corporation.  All rights reserved.

 

'zlib1.dll' is up-to-date

        if not exist C:\wireshark-win32-libs\zlib123 mkdir C:\wireshark-win32-libs\zlib123

        if not exist C:\wireshark-win32-libs\zlib123\lib mkdir C:\wireshark-win32-libs\zlib123\lib

        if not exist C:\wireshark-win32-libs\zlib123\include mkdir C:\wireshark-win32-libs\zlib123\include

        mt.exe -nologo -manifest "zlib1.dll.manifest" -outputresource:zlib1.dll;2

 

zlib1.dll.manifest : general error c1010070: Failed to load and parse the manifest. The system cannot find the file specified.

NMAKE : fatal error U1077: '"C:\Program Files\Microsoft SDKs\Windows\v7.0\bin\mt.exe"' : return code '0x1f'

Stop.

 

Anyone else seeing this?

- Chris

 

 

From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Abhik Sarkar
Sent: Monday, May 10, 2010 5:01 AM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] tshark (Windows) not working

 

I get the same error with dumpcap as well.

I went back to 32687 (there seem to be some major changes to dumpcap in 32688) and dumpcap works, but tshark gives the original error I reported:
E:\wireshark-src\wireshark-gtk2>dumpcap -i 2
File: C:\DOCUME~1\sarkara\LOCALS~1\Temp\wiresharkXXXXa01288
Packets: 31 Packets dropped: 0

E:\wireshark-src\wireshark-gtk2>tshark -i 2
Capturing on Intel(R) 82567LM Gigabit Network Connection
**
ERROR:column-utils.c:879:???: code should not be reached

E:\wireshark-src\wireshark-gtk2>

Then, I went back to 32682 (there are changes in 32683 to column-utils) and now it works at least.

So, I am staying here for now!

On Mon, May 10, 2010 at 10:02 AM, Abhik Sarkar <sarkar.abhik@xxxxxxxxx> wrote:

Hi Joan,

I am getting that error on both tshark and Wireshark with my build (32727) on Windows (32 bit). I tried doing a distclean; verify_tools; setup and build. It compiles without error, but refuses to capture. Looks like I chose a bad time to code a few changes ;-)

I haven't got around to investigating the issue in detail (yet)... I hope someone beats me to it.

Regards,
Abhik

 

On Sun, May 9, 2010 at 10:34 PM, j.snelders <j.snelders@xxxxxxxxxx> wrote:

Hi all,

SVN 32686
I get the same error (column-utils.c:879:???) running TShark on:
64-bit Windows 7, build 7600
64-bit Windows Server 2008 R2, build 7600


SVN 32692 and higher (the latest version I tried is SVN-32727):
Unable to capture with Wireshark and TShark, because "The capture session
could not be initiated ()" on:
64-bit Windows 7, build 7600
64-bit Windows Server 2008 R2, build 7600
Windows XP Service Pack 3, build 2600

$ tshark -D
1. \Device\NPF_{E859D76E-155B-4512-ACB6-B1B2A07914DB} (Intel(R) PRO/1000
MT Network Connection)

$ tshark -i 1
Capturing on Intel(R) PRO/1000 MT Network Connection
tshark: The capture session could not be initiated ().

Please check that "\Device\NPF_{E859D76E-155B-4512-ACB6-B1B2A07914DB}" is
the proper interface.
Help can be found at:
      http://wiki.wireshark.org/WinPcap
      http://wiki.wireshark.org/CaptureSetup
0 packets captured

Any ideas?

Thanks
Joan


On Thu, 6 May 2010 10:37:13 -0400 Chris Maynard wrote:
Yes, I?m seeing the same thing on Windows with the same SVN version, 32686.

From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx]

On Behalf Of Abhik Sarkar
Sent: Thursday, May 06, 2010 10:00 AM
To: Developer support list for Wireshark
Subject: [Wireshark-dev] tshark (Windows) not working

Hi All,

I can't get tshark to work anymore. I get this error:
E:\wireshark-src\wireshark-gtk2>tshark -i 2
Capturing on Intel(R) 82567LM Gigabit Network Connection
**
ERROR:column-utils.c:879:???: code should not be reached

E:\wireshark-src\wireshark-gtk2>

It seems to be related to the changes related to the timestamps which Stig
has been working on. Is anyone else facing issues?

I am on revision 32686.

Thanks,
Abhik.



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

 

 

CONFIDENTIALITY NOTICE: The contents of this email are confidential
and for the exclusive use of the intended recipient. If you receive this
email in error, please delete it from your system immediately and 
notify us either by email, telephone or fax. You should not copy,
forward, or otherwise disclose the content of the email.