Ethereal-dev: AW: [Ethereal-dev] Problems starting capturing

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: "Grossert, Alexander" <Alexander.Grossert@xxxxxxxxxxx>
Date: Thu, 16 Mar 2006 08:46:07 +0100
Title: Problems starting capturing
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?

Von: ethereal-dev-bounces@xxxxxxxxxxxx [mailto:ethereal-dev-bounces@xxxxxxxxxxxx] Im Auftrag von Dave Ramsey
Gesendet: Mittwoch, 15. März 2006 21:48
An: 'Ethereal development'
Betreff: RE: [Ethereal-dev] Problems starting capturing

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