|
Addition:
Hello.
I
investigated where the error occurs and it is obviously while trying to create
the dumpcap childprocess. I added some output to get the exact command line
called by ethereal and got this:
dumpcap -i
\Device\NPF_{06B77D3B-3C97-45FA-8AF9-C81A4EBAF823} -Z -B 1
When
calling this on the command line I only received some
rubbish:
F
4C:\DOCUME~1\nb223890\LOCALS~1\Temp\etherXXXX0UP95S P ♥1
D ♥0
When I
removed the "hidden feature" -Z from the command it started
capturing:
File: C:\DOCUME~1\nb223890\LOCALS~1\Temp\etherXXXX0UP95S
When I
tell ethereal to capture to a specific file the result is the
same.
Anyone
an idea what could be wrong with dumpcap now?
Hello
Dave,
thanks
for your suggestions. Regretably it did not solve the problem. I rebuilt
everything and made sure all files are where they should be and that PATH points
to all important directories.
Is
there a possibility to get some more output about what is going wrong, some kind
of log file or so?
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
| 
