From owner-freebsd-toolchain@freebsd.org Wed May 10 16:56:10 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 EEB59D66C61 for ; Wed, 10 May 2017 16:56:10 +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 DDA40B11 for ; Wed, 10 May 2017 16:56:10 +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 v4AGuAfF066790 for ; Wed, 10 May 2017 16:56:10 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 16:56:11 +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 16:56:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219153 --- Comment #6 from Mark Millard --- (In reply to John Baldwin from comment #5) I've used both gdb's as well but I've had more occasions when system's gdb worked and ports did not than the other way around (when there is a distinction). (Historically, not just now.) Okay I'll poke at ps -M and the /usr/local/bin/gdb crash. Be warned: I'm also currently evidence-gathering for two folks working on the clang powerpc and/or powerpc64 targeting support so my FreeBSD time is split. This also leads to context switching between a world built with gcc 4.2.1 and one built with clang. If I'm interrupted I can forget to switch and, for example, end up seeing the clang issues without initially noticing why (clang built system libraries, for example). I'll rerun the /usr/local/bin/gdb test explicitly on a gcc 4.2.1 built world just in case that happened yesterday. (clang generates powerpc and powerpc64 "code" that has handling of thrown-C++-exceptions completely broken, leading to segmentation faults while trying to reach landing-pad code. "Code": incomplete dwarf information.) --=20 You are receiving this mail because: You are the assignee for the bug.=