From: Jonny Grant <jg@jguk.org>
To: libc-help@sourceware.org
Subject: ld-linux-x86-64 core file SIGSEGV
Date: Sun, 21 Aug 2022 00:37:35 +0100 [thread overview]
Message-ID: <e7d8f49f-f8f9-b60b-745b-b3c14d5736b7@jguk.org> (raw)
Hello
I have a core file from a crash in glibc's ld.so
Couldn't reproduce it. Was just wondering if there was any useful info I could extract to identify which function it crashed in?
I can see the backtrace using 'bt' command.
I can see the assembly using 'layout asm'
Core was generated by `/lib64/ld-linux-x86-64.so.2 /usr/lib/vmware/lib/libvmware-modconfig.so/libvmwar'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fac33ccb540 in ?? ()
(gdb) bt
#0 0x00007fac33ccb540 in ()
#1 0x00007fac33ccea00 in ()
#2 0x00007fac33ccdfa0 in ()
#3 0x00007fac33c496b0 in ()
#4 0x00007fac33c49bf0 in ()
#5 0x00007fac33c4a130 in ()
#6 0x00007fac33ccd000 in ()
#7 0x00007fac33c4a670 in ()
#8 0x00007fac31cdf310 in () at /usr/lib/vmware/lib/libvmwarebase.so/libvmwarebase.so
installing libc6-amd64-dbgsym doesn't show any more
I'm running latest Ubuntu LTS. Just thought I would take a look, see if there is an issue.
$ /lib64/ld-linux-x86-64.so.2 --version
ld.so (Ubuntu GLIBC 2.35-0ubuntu3.1) stable release version 2.35.
Copyright (C) 2022 Free Software Foundation, Inc.
Cheers, Jonny
next reply other threads:[~2022-08-20 23:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 23:37 Jonny Grant [this message]
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
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=e7d8f49f-f8f9-b60b-745b-b3c14d5736b7@jguk.org \
--to=jg@jguk.org \
--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).