* Program terminated with signal 5, Trace/breakpoint trap
@ 2010-07-16 0:55 Mathew Yeates
2010-07-16 14:54 ` Jan Kratochvil
0 siblings, 1 reply; 6+ messages in thread
From: Mathew Yeates @ 2010-07-16 0:55 UTC (permalink / raw)
To: gdb
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Program terminated with signal 5, Trace/breakpoint trap
2010-07-16 0:55 Program terminated with signal 5, Trace/breakpoint trap Mathew Yeates
@ 2010-07-16 14:54 ` Jan Kratochvil
2010-07-16 15:52 ` Mathew Yeates
0 siblings, 1 reply; 6+ messages in thread
From: Jan Kratochvil @ 2010-07-16 14:54 UTC (permalink / raw)
To: Mathew Yeates; +Cc: gdb
On Fri, 16 Jul 2010 02:55:47 +0200, Mathew Yeates wrote:
[...]
> With gdb-7.2.50.20100713 I get this error while loading a corefile.
[...]
> x86_64 x86_64 x86_64 GNU/Linux
[...]
> "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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Program terminated with signal 5, Trace/breakpoint trap
2010-07-16 14:54 ` Jan Kratochvil
@ 2010-07-16 15:52 ` Mathew Yeates
2010-07-16 16:00 ` Mathew Yeates
2010-07-16 16:04 ` Jan Kratochvil
0 siblings, 2 replies; 6+ messages in thread
From: Mathew Yeates @ 2010-07-16 15:52 UTC (permalink / raw)
To: Jan Kratochvil; +Cc: gdb
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
<jan.kratochvil@redhat.com> wrote:
> On Fri, 16 Jul 2010 02:55:47 +0200, Mathew Yeates wrote:
> [...]
>> With gdb-7.2.50.20100713 I get this error while loading a corefile.
> [...]
>> x86_64 x86_64 x86_64 GNU/Linux
> [...]
>> "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
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Program terminated with signal 5, Trace/breakpoint trap
2010-07-16 15:52 ` Mathew Yeates
@ 2010-07-16 16:00 ` Mathew Yeates
2010-07-16 16:06 ` Jan Kratochvil
2010-07-16 16:04 ` Jan Kratochvil
1 sibling, 1 reply; 6+ messages in thread
From: Mathew Yeates @ 2010-07-16 16:00 UTC (permalink / raw)
To: Jan Kratochvil; +Cc: gdb
I just noticed another warning
"warning: no loadable sections found in added symbol-file
system-supplied DSO at 0x2aaaaaaab000"
On Fri, Jul 16, 2010 at 8:52 AM, Mathew Yeates <mat.yeates@gmail.com> wrote:
> 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
> <jan.kratochvil@redhat.com> wrote:
>> On Fri, 16 Jul 2010 02:55:47 +0200, Mathew Yeates wrote:
>> [...]
>>> With gdb-7.2.50.20100713 I get this error while loading a corefile.
>> [...]
>>> x86_64 x86_64 x86_64 GNU/Linux
>> [...]
>>> "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
>>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Program terminated with signal 5, Trace/breakpoint trap
2010-07-16 15:52 ` Mathew Yeates
2010-07-16 16:00 ` Mathew Yeates
@ 2010-07-16 16:04 ` Jan Kratochvil
1 sibling, 0 replies; 6+ messages in thread
From: Jan Kratochvil @ 2010-07-16 16:04 UTC (permalink / raw)
To: Mathew Yeates; +Cc: gdb
On Fri, 16 Jul 2010 17:52:40 +0200, Mathew Yeates wrote:
> 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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2010-07-16 16:06 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-07-16 0:55 Program terminated with signal 5, Trace/breakpoint trap Mathew Yeates
2010-07-16 14:54 ` Jan Kratochvil
2010-07-16 15:52 ` Mathew Yeates
2010-07-16 16:00 ` Mathew Yeates
2010-07-16 16:06 ` Jan Kratochvil
2010-07-16 16:04 ` Jan Kratochvil
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).