Wireshark-dev: Re: [Wireshark-dev] Crash after Init dissectors (read_hosts_file)

From: Shelly Cadora <scadora@xxxxxxxxx>
Date: Wed, 20 Sep 2006 12:20:26 -0700 (PDT)
Maybe I'm getting a little closer here... 
 
It looks like fgetline is failing when it tries to read from the hosts file.  The file pointer returned by eth_fopen(hostspath, "r") in the read_hosts_file function is bad.  I don't understand why...hostspath is correct (C:\WINNT\system32\drivers\etc\hosts) and the hosts file exists and is readable.
Anybody have any suggestions?
 
Thanks,
Shelly

Shelly Cadora <scadora@xxxxxxxxx> wrote:
Alas, I have arrived at the same place.  If I understand MSVC's debugging function correctly (questionable), then it's crashing at an fgetline call in libwireshark.dll.

> libwireshark.dll!fgetline(char * * buf=0x0012fc20, int * size=0x0012fc1c, _iobuf * fp=0x77c5fce0)  Line 588 + 0xa bytes C
That's all I've got so far.  This is wireshark 0.99.4.0.  Let me know if you find anything.
 
Shelly
------------------------------

Message: 4
Date: Tue, 19 Sep 2006 17:28:20 -0700 (PDT)
From: Andrew Feren
Subject: Re: [Wireshark-dev] newbie build problem with python ->
gnutls/openssl.h
To: Developer support list for Wireshark
Message-ID: <20060920002820.17901.qmail@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=iso-8859-1

If you get it to run let me know how. I got it to run as far as the little
blurb that says "Init dissectors...". Then it crashes.

I haven't made much progress beyond that. I've been wrestling with windbg.

-Andrew

--- Shelly Cadora wrote:

> Great! That did the trick. It doesn't *run*, but at least it compiles...
>
> Thanks for the suggestion,
> Shelly
>

Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates starting at 1�/min._______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev


Do you Yahoo!?
Get on board. You're invited to try the new Yahoo! Mail.