public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Mathew Yeates <mat.yeates@gmail.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: Program terminated with signal 5, Trace/breakpoint trap
Date: Fri, 16 Jul 2010 16:00:00 -0000	[thread overview]
Message-ID: <AANLkTilqdk_WC3oydZpUkCS8eM50kYUeCxJZedXZm-yA@mail.gmail.com> (raw)
In-Reply-To: <AANLkTims9GMpc70SM180_zfQjoWLlrRzm3W32KWkNtsu@mail.gmail.com>

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
>>
>

  reply	other threads:[~2010-07-16 16:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-16  0:55 Mathew Yeates
2010-07-16 14:54 ` Jan Kratochvil
2010-07-16 15:52   ` Mathew Yeates
2010-07-16 16:00     ` Mathew Yeates [this message]
2010-07-16 16:06       ` Jan Kratochvil
2010-07-16 16:04     ` Jan Kratochvil

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTilqdk_WC3oydZpUkCS8eM50kYUeCxJZedXZm-yA@mail.gmail.com \
    --to=mat.yeates@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).