From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id D86843858401 for ; Mon, 22 Aug 2022 06:41:41 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org D86843858401 Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-1-hL5lQTkwNvW176vNJTb9sQ-1; Mon, 22 Aug 2022 02:41:39 -0400 X-MC-Unique: hL5lQTkwNvW176vNJTb9sQ-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 00EE429ABA2B; Mon, 22 Aug 2022 06:41:39 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.39.192.199]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 52832909FF; Mon, 22 Aug 2022 06:41:38 +0000 (UTC) From: Florian Weimer To: Jonny Grant Cc: libc-help@sourceware.org Subject: Re: ld-linux-x86-64 core file SIGSEGV References: Date: Mon, 22 Aug 2022 08:41:36 +0200 In-Reply-To: (Jonny Grant's message of "Sun, 21 Aug 2022 00:37:35 +0100") Message-ID: <87a67w6aqn.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.11.54.5 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-5.5 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: libc-help@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-help mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2022 06:41:43 -0000 * Jonny Grant: > 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/li= bvmware-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/lib= vmwarebase.so > > > installing libc6-amd64-dbgsym doesn't show any more Sometimes it's possible to get better backtraces by loading the symbol table for the name program using =E2=80=9Cfile=E2=80=9D, running ld.so and = the program under the debugger, or both. I've got a request open with our GDB developers to improve debugging with an explicit ld.so invocation, but so far, it's a known issue. Thanks, Florian