1. eugtk - segmentation fault
I'm in the process of translating my Diet Monger Ass Kicker program to
eugtk. I very slowly got thru most of four out of seven files without any
errors caught by the interpreter. Major learning experience, gtk is a new
thing for me. Then I ran into something called "segmentation fault". I
looked up "segmentation fault" on google and it has to do with either a
dangling pointer or something trying to access memory that it's not supposed
to access. Too technical for me to understand. The error message says just
"segmentation fault", no line number, no furthur information.
The question is: how do I track it down?
2. eugtk - segmentation fault
I'm in the process of translating my Diet Monger Ass Kicker program to
eugtk. I very slowly got thru most of four out of seven files without any
errors caught by the interpreter. Major learning experience, gtk is a new
thing for me. Then I ran into something called "segmentation fault". I
looked up "segmentation fault" on google and it has to do with either a
dangling pointer or something trying to access memory that it's not supposed
to access. Too technical for me to understand. The error message says just
"segmentation fault", no line number, no furthur information.
The question is: how do I track it down?
3. Re: eugtk - segmentation fault
Hello Jerry!
You are right. A segmentation fault is typically, but not always, a pointer
problem, such
as referencing a null pointer, for instance. What you need to do is run a trace
on your
Euphoria code, and determine what the last line is that runs before the
segmentation fault
occurs. When you discover this magic last line, more than likely you'll find a
Euphoria
routine which wraps a GTK function that takes a pointer. GTK, like most C
libraries, uses
pointers extensively. Usually when I have this problem with GTK and Linux
(don't have a
Linux distro installed atm), it is because the C function calls for a pointer to
a pointer
to a pointer, i.e., char ***goofy, or something of that nature.
I hope this helps. Once you find the region that is causing the segfault, you
might
consider posting that bit of code to the list, to see if we can figure out what
is going on
from there.
Travis Beaty
Mason City, Iowa.
9/26/2002 4:28:08 PM, Jerry Story <jstory at edmc.net> wrote:
>
>
> I'm in the process of translating my Diet Monger Ass Kicker program to
>eugtk. I very slowly got thru most of four out of seven files without any
>errors caught by the interpreter. Major learning experience, gtk is a new
>thing for me. Then I ran into something called "segmentation fault". I
>looked up "segmentation fault" on google and it has to do with either a
>dangling pointer or something trying to access memory that it's not supposed
>to access. Too technical for me to understand. The error message says just
>"segmentation fault", no line number, no furthur information.
> The question is: how do I track it down?
>
>
>
>
