Thread: seg fault with any function call

Make a small test program that only calls the function in question, or provides the absolute minimum information required to make the function work. If it works fine, it's something else in your program. You might also consider compiling with debug flags enabled so it dumps a core file, which you can use with GDB.


Quzah.

Sounds to me like you have a stack overflow - that will fail when you call a new function, because that will try to write to the lowest address in the stack.

Of course, it could be 101 other things too.

--
Mats

You could try using a debugger to find out more about the problem and perhaps post your code.

You could also try commenting out parts of the code to see whether it makes the program behave correctly. But this may not always work: a few hours ago I "narrowed down" a segfault to a line that looked like x = 1; With that line uncommented everything appeared to work normally. (The real error most probably was completely elsewhere: I had forgotten to override a function in a different class that according to the manual must always be overridden.)

It is fairly typical what you describe - all is well within one function, then call another and it blows up. I have seen it in kernel code quite a few times. I usually don't get it in user-mode code, but it can happen.

--
Mats