From owner-freebsd-toolchain@freebsd.org Wed May 10 15:53:14 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 12047D672A1 for ; Wed, 10 May 2017 15:53:14 +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 00FBB16F2 for ; Wed, 10 May 2017 15:53:14 +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 v4AFrDIb005882 for ; Wed, 10 May 2017 15:53:13 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 15:53:13 +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: 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 15:53:14 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219153 --- Comment #5 from John Baldwin --- I would start with trying to debug why 'ps -M' doesn't work by stepping thr= ough 'ps'. In terms of gdb7 vs gdb6, I definitely used gdb7 on userland binaries with threads, fork following, etc. last year under qemu for ppc64. The gdb port= has a DEBUG option that will build gdb with debug symbols. Can you build your = gdb port with that (if not already enabled) and get a stack trace from the gdb.core? You can use /usr/libexec/gdb to examine the core of gdb7 for now= .=20 Alternatively, you can grab the a.out and core file from a ppc system and d= ebug it using the gdb binary from ports on an amd64 host (the ports gdb includes cross-debugging of user cores for all supported architectures). It may be = that the amd64 gdb7 also cores, but if so you will be able to debug the amd64 gd= b7 using a native gdb7 on amd64. --=20 You are receiving this mail because: You are the assignee for the bug.=