Hi Alexander \o/ …
I had the same problem once … Make sure
that dumpcap.exe is in the same folder as ethereal.exe …
(As you suggested, perhaps it only needs
to be on the PATH)
You will get that error message if dumpcap
can’t be executed.
Regards,
Dave
From:
ethereal-dev-bounces@xxxxxxxxxxxx [mailto:ethereal-dev-bounces@xxxxxxxxxxxx] On Behalf Of Grossert, Alexander
Sent: 15 March 2006 08:02
To: ethereal-dev@xxxxxxxxxxxx
Subject: [Ethereal-dev] Problems
starting capturing
Hello.
I lately started developing ethereal, especially concerning protocoll plugins.
First
I installed ethereal normally to learn about it. Then I built up the dev
environment with all the libs and src.
At
first I followed the foo protocoll example from the dev's guide to understand
how it is done.
When I
finally made everything compile the correct way I started ethereal and the
protocoll was
enlisted.
But when I wanted to start a live capture the most easiest way (clicking on
capture in the interface menu)
A
message popped up telling me that no child process could be spawn due to a bad
file descriptor.
The
same thing happened when I installed the plugin into the normal installation of
ethereal from the beginning.
I
deinstalled the program and built the sources again and the problem was still
there.
Has
anyone an idea? Could it be some problem with the PATH?
Thanks
in advance
