random error

[Fozzy]

Anyone know how to find the cause of an error where a C++ program gives
a SIG fault when creating something. The thing is any old random thing
that is created. I can't find any good reason...

Cheers for any help

 

[Victor Bazarov]

Anyone know how to find the cause of an error where a C++ program gives
a SIG fault when creating something.

What's "something" and what do you mean by "creating"? Opening a file?
Allocating a dynamic object?

The thing is any old random thing

What do you mean by "random"?

that is created. I can't find any good reason...

I can't claim understanding of your problem. I don't mean to be rude,
but perhaps you could try to be a bit more specific?

Have you tried running your process under a debugger? I would expect
most modern debuggers to be able to catch a segmentation fault (I am not
sure what a SIG fault is, though).

 

[Barney]

Anyone know how to find the cause of an error where a C++ program gives
a SIG fault when creating something. The thing is any old random thing
that is created. I can't find any good reason...

Cheers for any help

Have you tried remaking everything??

 

[Fozzy]

Have you tried remaking everything??

Yes, cheers

 

[David Harmon]

On Wed, 19 Jan 2005 16:04:08 +0000 in comp.lang.c++, Fozzy

Anyone know how to find the cause of an error where a C++ program gives
a SIG fault when creating something. The thing is any old random thing
that is created. I can't find any good reason...

That most commonly means that something earlier, perhaps much earlier
in the execution of the program, has gone wrong in such a way as to
damage the free memory pool structures. It could be the result of
anything defined as "undefined behavior". Most common thing in my
opinion is writing through an uninitialized pointer.
What is the code like?

 

[Fozzy]

On Wed, 19 Jan 2005 16:04:08 +0000 in comp.lang.c++, Fozzy



That most commonly means that something earlier, perhaps much earlier
in the execution of the program, has gone wrong in such a way as to
damage the free memory pool structures. It could be the result of
anything defined as "undefined behavior". Most common thing in my
opinion is writing through an uninitialized pointer.
What is the code like?

The code is gigantic with pointers flying about everywhere, which makes
finding any such error very difficult. Thanks for the advice anyway.

Cheers