From owner-freebsd-toolchain@freebsd.org  Wed May 10 23:25:12 2017
Return-Path: <owner-freebsd-toolchain@freebsd.org>
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 D57E0D67AC7
 for <freebsd-toolchain@mailman.ysv.freebsd.org>;
 Wed, 10 May 2017 23:25:12 +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 C46A8131B
 for <freebsd-toolchain@FreeBSD.org>; Wed, 10 May 2017 23:25:12 +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 v4ANPCbs022962
 for <freebsd-toolchain@FreeBSD.org>; Wed, 10 May 2017 23:25:12 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 23:25:12 +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: jhb@FreeBSD.org
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: <bug-219153-29464-uuFVCT6JGU@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-219153-29464@https.bugs.freebsd.org/bugzilla/>
References: <bug-219153-29464@https.bugs.freebsd.org/bugzilla/>
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
 <freebsd-toolchain.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-toolchain/>
List-Post: <mailto:freebsd-toolchain@freebsd.org>
List-Help: <mailto:freebsd-toolchain-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 May 2017 23:25:12 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219153

--- Comment #8 from John Baldwin <jhb@FreeBSD.org> ---
Can you pop up to frame 13 (solib_svr4_r_map) and 'p *info' and 'p *lmo'?  =
The
lack of working exceptions from clang (which appears to be the source of the
coredump in gdb itself) might be problematic though.  gdb might very well
depend on working exceptions to work properly.  The current gdb7.12.1 can be
compiled with gcc4.2.1 still which might work better than compiling with cl=
ang.
 The next gdb release (8.0) requires C++11 which will need an external gcc =
or
fully functional clang.  I've been using mips-gcc to build gdb 'master' for
FreeBSD/mips just fine against a MIPS world built via mips-xtoolchain-gcc (=
both
32-bit and 64-bit).

--=20
You are receiving this mail because:
You are the assignee for the bug.=