wireshark-dev October 2010 archive
Main Archive Page > Month Archives  > wireshark-dev archives
wireshark-dev: Re: [Wireshark-dev] Seg Fault - Creating new wire

Re: [Wireshark-dev] Seg Fault - Creating new wiretap type

From: Alex Lindberg <alindber_at_nospam>
Date: Thu Oct 21 2010 - 21:42:34 GMT
To: Developer support list for Wireshark <wireshark-dev@wireshark.org>

That was my thought, however I used a debugger and printf statements to watch the file handle passed to the wiretap routines. The file was the same in all cases. This has me stumped.
It seems that my string buffer is not allowed during the file_gets routing. Perhaps making the buffer a const for the procedure, but that is not necessary in other modules.

--- On Thu, 10/21/10, Stephen Fisher <steve@stephen-fisher.com> wrote:

From: Stephen Fisher <steve@stephen-fisher.com>
Subject: Re: [Wireshark-dev] Seg Fault - Creating new wiretap type
To: "Developer support list for Wireshark" <wireshark-dev@wireshark.org>
Date: Thursday, October 21, 2010, 2:16 PM

On Thu, Oct 21, 2010 at 05:03:12AM -0700, Alex Lindberg wrote:

> When trying to read the first line during the initial myfile_open
> routine, the file_gets or file_read fail with a segmentation fault. If
> I do my own fopen for the filename, all is good, but when using
> wth->fh, it fails. I have copied the format found in other wiretap/*c
> files and don't see my error.

Have you run it through a debugger? The file handle may not be a valid
pointer for some reason.
___________________________________________________________________________
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

___________________________________________________________________________
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