Wireshark mailing list archives
Re: Python error: "execvp: bad file number"
From: Gisle Vanem <gvanem () broadpark no>
Date: Fri, 17 Feb 2012 19:28:02 +0100
"Graham Bloice" <graham.bloice () trihedral com> 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 lines ("wc -c foo"). Isn't each env-var separated by a 0 in a block somewhere? Hence env-size ~= size of foo - lines in foo.
(since each line has a '\r\n' termination).--gv ___________________________________________________________________________
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-request () wireshark org?subject=unsubscribe
Current thread:
- Python error: "execvp: bad file number" Gisle Vanem (Feb 17)
- Re: Python error: "execvp: bad file number" Graham Bloice (Feb 17)
- Re: Python error: "execvp: bad file number" Gisle Vanem (Feb 17)
- Re: Python error: "execvp: bad file number" Graham Bloice (Feb 17)