Re: [Wireshark-dev] Python error: "execvp: bad file number"

2012-02-17 Thread Gisle Vanem
"Graham Bloice" wrote: I built on the same platform just a few minutes ago (from trunk r41048) and register.c was fine. I'm using python 2.7.1 though. How are you determining your environment size? I'm sure the is a function for this, but I approximated by a "set > foo", counting the lin

Re: [Wireshark-dev] Python error: "execvp: bad file number"

2012-02-17 Thread Graham Bloice
> I hit a problem with the Python generation of epan/dissectors/register.c. > The message from my python (v. 2.7.2) at this stage was: > > .. "execvp: python: Bad file number" > > after reading the docs on '_execvp' [1] at MSDN, I suspect this error is related > to the very long command-line giv

[Wireshark-dev] Python error: "execvp: bad file number"

2012-02-17 Thread Gisle Vanem
I hit a problem with the Python generation of epan/dissectors/register.c. The message from my python (v. 2.7.2) at this stage was: .. "execvp: python: Bad file number" after reading the docs on '_execvp' [1] at MSDN, I suspect this error is related to the very long command-line given to pytho