From: Jonny Grant <jg@jguk.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-help@sourceware.org
Subject: Re: ld-linux-x86-64 core file SIGSEGV
Date: Mon, 22 Aug 2022 11:47:29 +0100 [thread overview]
Message-ID: <34136fcb-da3c-f8f7-d091-ec1c8b3c187e@jguk.org> (raw)
In-Reply-To: <87o7wczhgi.fsf@oldenburg.str.redhat.com>
On 22/08/2022 11:43, Florian Weimer wrote:
> * Jonny Grant:
>
>> I got it to load the debug symbol using "file" command you
>> mentioned. Unfortunately backtrace still empty. The debug symbols
>> /usr/lib/debug/.build-id/61/ef896a699bb1c2e4e231642b2e1688b2f1a61e.debug
>> are only 592,952 bytes
>>
>> I would probably just prefer if binaries weren't separated from their
>> debug symbols. Do you know any distributions that don't strip symbols
>> from glibc?
>
> I'm not sure if this is caused by debuginfo separation. I run into GDB
> when I use my own custom-built glibc with unstripped debuginfo.
>
> Anyway, you can probably use eu-unstrip from elfutils to undo the
> debuginfo separation.
>
> Thanks,
> Florian
That's a good tip than you.
I did use objdump -d on the ld.so, but couldn't spot anything similar to what I saw in "layout asm" from gdb.
Is it ever possible to match up disassembly with the gdb core disassembly this way?
Cheers, Jonny
next prev parent reply other threads:[~2022-08-22 10:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 23:37 Jonny Grant
2022-08-22 6:41 ` Florian Weimer
2022-08-22 10:26 ` Jonny Grant
2022-08-22 10:43 ` Florian Weimer
2022-08-22 10:47 ` Jonny Grant [this message]
2022-08-22 10:52 ` Florian Weimer
2022-08-22 16:29 ` Jonny Grant
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=34136fcb-da3c-f8f7-d091-ec1c8b3c187e@jguk.org \
--to=jg@jguk.org \
--cc=fweimer@redhat.com \
--cc=libc-help@sourceware.org \
/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).