From owner-freebsd-toolchain@freebsd.org  Sun May 14 22:13:52 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 BF0E6D6D07C
 for <freebsd-toolchain@mailman.ysv.freebsd.org>;
 Sun, 14 May 2017 22:13:52 +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 ADBF61FE1
 for <freebsd-toolchain@FreeBSD.org>; Sun, 14 May 2017 22:13:52 +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 v4EMDqi5076464
 for <freebsd-toolchain@FreeBSD.org>; Sun, 14 May 2017 22:13:52 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: Sun, 14 May 2017 22:13:52 +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: <bug-219153-29464-PDEFOhxZgR@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: Sun, 14 May 2017 22:13:52 -0000

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

--- Comment #15 from Mark Millard <markmi@dsl-only.net> ---
(In reply to Mark Millard from comment #14)

FYI:

Part of the reason for the HACK status for
debug.minidump=3D0 is that for old PowerMac's,
while the loader handles the relocatable
format, it does not actually relocate
the kernel: The result of the kernel load
still matches the debug information.

Stored virtual vs. dumped physical addresses
when the values are distinct would be an issue
on various powerpc's for memory references
where it matters.

The code depends on such loading and only
handles physical=3D=3Dvirtual contexts for
debug.minidump=3D0 .

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