Discussion:
Program terminated with signal 5, Trace/breakpoint trap
Mathew Yeates
2010-07-16 00:55:47 UTC
Permalink
Hi
With gdb-7.2.50.20100713 I get this error while loading a corefile.

uname
x86_64 x86_64 x86_64 GNU/Linux

gcc -v
gcc-4.2.4

the first potential error I see, prior to "Program terminated with
signal 5, Trace/breakpoint trap" is
"warning: Can't read pathname for load map: Input/output error."

Help?

-Mathew
Jan Kratochvil
2010-07-16 14:54:33 UTC
Permalink
On Fri, 16 Jul 2010 02:55:47 +0200, Mathew Yeates wrote:
[...]
Post by Mathew Yeates
With gdb-7.2.50.20100713 I get this error while loading a corefile.
[...]
Post by Mathew Yeates
x86_64 x86_64 x86_64 GNU/Linux
[...]
Post by Mathew Yeates
"warning: Can't read pathname for load map: Input/output error."
I think you face this one:
[patch] Fix GNU/Linux core open: Can't read pathname for load map: Input/output error.
http://sourceware.org/ml/gdb-patches/2009-10/msg00142.html

OTOH I still believe the right fix would be in glibc (referenced there).


Regards,
Jan
Mathew Yeates
2010-07-16 15:52:40 UTC
Permalink
After looking at the patch, it looks like the warning I was seeing was
harmless and probably not responsible for my program terminating.
Right?

On Fri, Jul 16, 2010 at 7:54 AM, Jan Kratochvil
[...]
Post by Mathew Yeates
With gdb-7.2.50.20100713 I get this error while loading a corefile.
[...]
Post by Mathew Yeates
 x86_64 x86_64 x86_64 GNU/Linux
[...]
Post by Mathew Yeates
"warning: Can't read pathname for load map: Input/output error."
       [patch] Fix GNU/Linux core open: Can't read pathname for load map: Input/output error.
       http://sourceware.org/ml/gdb-patches/2009-10/msg00142.html
OTOH I still believe the right fix would be in glibc (referenced there).
Regards,
Jan
Mathew Yeates
2010-07-16 15:59:54 UTC
Permalink
I just noticed another warning
"warning: no loadable sections found in added symbol-file
system-supplied DSO at 0x2aaaaaaab000"
Post by Mathew Yeates
After looking at the patch, it looks like the warning I was seeing was
harmless and probably not responsible for my program terminating.
Right?
On Fri, Jul 16, 2010 at 7:54 AM, Jan Kratochvil
[...]
Post by Mathew Yeates
With gdb-7.2.50.20100713 I get this error while loading a corefile.
[...]
Post by Mathew Yeates
 x86_64 x86_64 x86_64 GNU/Linux
[...]
Post by Mathew Yeates
"warning: Can't read pathname for load map: Input/output error."
       [patch] Fix GNU/Linux core open: Can't read pathname for load map: Input/output error.
       http://sourceware.org/ml/gdb-patches/2009-10/msg00142.html
OTOH I still believe the right fix would be in glibc (referenced there).
Regards,
Jan
Jan Kratochvil
2010-07-16 16:06:06 UTC
Permalink
Post by Mathew Yeates
I just noticed another warning
"warning: no loadable sections found in added symbol-file
system-supplied DSO at 0x2aaaaaaab000"
This was an issue on some x86_64 Linux kernels with 8KB vDSO (instead of
common 4KB). There was Fedora GDB workaround for it but recent Linux kernels
do not need the workaround as they have 4KB vDSO again.
https://bugzilla.redhat.com/show_bug.cgi?id=312011


Regards,
Jan

Jan Kratochvil
2010-07-16 16:03:53 UTC
Permalink
Post by Mathew Yeates
After looking at the patch, it looks like the warning I was seeing was
harmless and probably not responsible for my program terminating.
Right?
Yes. There is either some forgotten breakpoint in the inferior or some
un-waitpid()ed SIGTRAP signal left in the inferior, just guessing.


Regards,
Jan
Loading...