From owner-freebsd-toolchain@freebsd.org Wed May 10 00:59:02 2017 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 22E6CD65260 for ; Wed, 10 May 2017 00:59:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F2E061F53 for ; Wed, 10 May 2017 00:59:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4A0x1lV013466 for ; Wed, 10 May 2017 00:59:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-toolchain@FreeBSD.org Subject: [Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such Date: Wed, 10 May 2017 00:59:02 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markmi@dsl-only.net X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-toolchain@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 May 2017 00:59:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219153 --- Comment #4 from Mark Millard --- A not as libkvm tied note about which gdb works better for 32-bit powerpc in at least some contexts: I took an a.out (from clang++=20 targeting powerpc) and tried /usr/local/bin/gdb and /usr/libexec/gdb on a core it generated: # gdb a.out /var/crash/a.out.29973.core=20 GNU gdb (GDB) 7.12.1 [GDB v7.12.1 for FreeBSD] . . . Core was generated by `./a.out'. Program terminated with signal SIGSEGV, Segmentation fault. Segmentation fault (core dumped) (gdb itself Segmentation faulted.) # /usr/libexec/gdb a.out /var/crash/a.out.29973.core GNU gdb 6.1.1 [FreeBSD] . . . Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libc++.so.1...Reading symbols from /usr/lib/debug//usr/lib/libc++.so.1.debug...done. . . . Loaded symbols for /libexec/ld-elf.so.1 #0 0x41b355d0 in _Unwind_SetGR (context=3D, index=3D<= value optimized out>, val=3D1105281072) at unwind-dw2-fde.h:162 162 { (gdb) bt #0 0x41b355d0 in _Unwind_SetGR (context=3D, index=3D<= value optimized out>, val=3D1105281072) at unwind-dw2-fde.h:162 #1 0x4192e370 in __gxx_personality_v0 (version=3D, actions=3D, exceptionObject=3D0x41e14030, context=3D0x= ffffd5c0) at /usr/src/contrib/libcxxrt/exception.cc:1203 #2 0x41b36234 in _Unwind_RaiseException_Phase2 (exc=3D, context=3D) at unwind.inc:66 #3 0x41b35e10 in _Unwind_RaiseException (exc=3D0xffffd5c0) at unwind.inc:1= 35 #4 0x4192d870 in __cxa_throw (thrown_exception=3D, tinfo=3D, dest=3D) at /usr/src/contrib/libcxxrt/exception.cc:774 #5 0x01800954 in main () at exception_test.cpp:5 Current language: auto; currently minimal The same thing happens for running the a.out inside gdb: /usr/local/bin/gdb gets a Segmentation fault of its own and /usr/libexec/gdb works, including allowing the bt. Historically I've primarily used the system gdb to do my analysis of clang's code generation problems for targeting powerpc. Including when I looked at gcc 4.2.1 generated code for comparison. The above sort of thing is an example of why. --=20 You are receiving this mail because: You are the assignee for the bug.=