topic Segmentation fault in Operating System - Linux

Segmentation fault

subrat chaudhary — Wed, 16 May 2007 04:33:30 GMT

I have found a segmentation error for a c++ application:

Program terminated with signal 11, Segmentation fault.
SEGV_MAPERR - Address not mapped to object
Error trying to get information about dynamic linker.
#0 0xc0000000000cc260 in ()

can anyone help me...
Thanks in advance.
Regards,
Subrat

Re: Segmentation fault

Hein van den Heuvel — Wed, 16 May 2007 07:10:49 GMT

What is the history here?
Is this a new program?
Home grown or 3rd party?
Did it ever work?
What changed?

If I had to investigate this problem for real, then I would start with analyzing the progam you are trying to run with 'ldd' and check the PATH, LD_LIBRARY_PATH and application environment variables.

Check the man pages for ldd and dld.sl

If that did not point me in the right direction, then I would run the program with trace, let the (reams of) output scroll by untill the problem happens. Then scroll back a screen or two looking for a failing (dlopen?) call.

Hope this helps some,
Hein van den Heuvel (at gmail dot com)
HvdH Performance Consulting

Re: Segmentation fault

Dennis Handly — Wed, 16 May 2007 21:51:13 GMT

What version of gdb do you have? The latest is 5.6.

Was the above output from a core file? If you have a corefile, you must debug it on the system it occurs, or use the packcore/unpackcore commands to move it to another system.

The address above looks like you are aborting in a readonly shared lib. Can you get a stack trace with "bt"?

Once you get that, you could compile with -g so you can query the local variables of the function in question.