Hi

Which mauals to read when confronted with errors like Seg. Fault. I
have already asked this question, but I thought I'd pose it again. How
to know the meaning of Error messages, they aren't listed in any C
book. Also I have few doubts, I was wondering if someone could kindly
chat with me on Yahoo MSN. Google takes 3-6 hrs to post :(

Thx
Grumple

"grumple" <forgoogle2003@yahoo.co.in> wrote in message
>
> Which mauals to read when confronted with errors like Seg. Fault. I
> have already asked this question, but I thought I'd pose it again. How
> to know the meaning of Error messages, they aren't listed in any C
> book. Also I have few doubts, I was wondering if someone could
> kindly chat with me on Yahoo MSN. Google takes 3-6 hrs to post :(
>
A segmentation fault is the only runtime error that you are likely to
encounter in C programming. It means that the application is trying to
access memory that it doesn't own.
There can be several reasons, an array overrun, an attempt to access memory
that has been freed, or a corruot pointer. Most debuggers tell you where the
segementation violation occurred, then you simply have to work out what went
wrong.

Malcolm wrote:
> 
> "grumple" <forgoogle2003@yahoo.co.in> wrote in message
> >
> > Which mauals to read when confronted with errors like Seg. Fault. I
> > have already asked this question, but I thought I'd pose it again. How
> > to know the meaning of Error messages, they aren't listed in any C
> > book. Also I have few doubts, I was wondering if someone could
> > kindly chat with me on Yahoo MSN. Google takes 3-6 hrs to post :(
> >
> A segmentation fault is the only runtime error that you are likely to
> encounter in C programming. It means that the application is trying to
> access memory that it doesn't own.
> There can be several reasons, an array overrun, an attempt to access memory
> that has been freed, or a corruot pointer. Most debuggers tell you where the
> segementation violation occurred, then you simply have to work out what went
> wrong.
>
A "segmentation fault" is *not* specific to the C language.
You can get a segmentation fault with assembly language too.

--
+----------------------------------------------------------------+
|   Charles and Francis Richmond     richmond at plano dot net   |
+----------------------------------------------------------------+

grumple wrote:
> 
> Which mauals to read when confronted with errors like Seg. Fault.
> I have already asked this question, but I thought I'd pose it
> again. How to know the meaning of Error messages, they aren't
> listed in any C book.

Refer to your OS manuals.

> Also I have few doubts, I was wondering if someone could kindly
> chat with me on Yahoo MSN. Google takes 3-6 hrs to post :(

So don't use google.  Install a newsreader.  Netscape is simple.

--
Replies should be to the newsgroup
Chuck Falconer, on vacation.

"Charles Richmond" <richmond@ev1.net> wrote in message
>
> A "segmentation fault" is *not* specific to the C language.
> You can get a segmentation fault with assembly language too.
>
Sure. But if you are programming in C you are very likely to get a
segmentation fault at run-time, not very likely to get an illegal
instruction or other error. This is because C makes it easy to access the
wrong chunk of memory, but makes it difficult to jump to an invalid code
page.