ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] pre-commit ImportError

From: Graham Bloice <graham.bloice@xxxxxxxxxxxxx>
Date: Wed, 17 Feb 2016 11:11:54 +0000

On 17 February 2016 at 09:17, João Valverde <joao.valverde@xxxxxxxxxxxxxxxxxx> wrote:
On 17-02-2016 09:07, POZUELO Gloria (BCS/PSD) wrote:
Using git bash and typing python shows me the following message:  "cygheap base mismatch detected. This problem is probably due to using incompatible versions of the Cygwin DLL."

I'm no Windows expert but I think that means Cygwin python comes before Win32 python on your (git bash) PATH.

This may be a long-standing nit of mine with Windows Wireshark development environments.

Unless you really have a need, e.g. for other work on the same machine, then do NOT put Cygwin on your path, it has in the past caused all kinds of issues.  Both nmake and CMake have mechanisms to locate Cygwin as required.

If you must have Cygwin on the path for other tasks, then you may be better off creating a VM for your Wireshark work that doesn't put Cygwin on the path.  This is the method I've used for a number of years as it allows me to isolate and control the Wireshark build env on machines that are normally used for building other software as part of the day job.

A further bump along this path :-), is Git.  You must make sure you install Git without the option "Use Git and optional Unix tools from the Windows Command Prompt" as this then interferes with CMake finding the Cygwin tools we want.

For Python, I have both the Windows native Python directory (e.g. C:\Python27) and the Python scripts directory (e.g. C:\Python27\Scripts) on my path, the latter for git-review.

Graham Bloice