From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 291D4385843A; Wed, 21 Dec 2022 20:15:08 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 291D4385843A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1671653708;
	bh=4ZdGowaJsF4vOLVG7oVJKuA5MjEUPBNJarO8b8Q3CEI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=lRbKsbDZ/zzlsVYZsXOcfc1rT0SB4k+YsdSSGWkkTQSeTD2N87qn7x8x8tJ3XRfgJ
	 YXnyZQS24y+mvz5vQOWcz3BCTh6UN3jBzgcJJwdVQlVjuQFGbNFs9655b5D57fMGSl
	 ijNQFQS7pw3AwrR7m8bnLFZk1iiUST2GU4h4zoxM=
From: "ariscop at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/20007] 'section' command doesn't work
Date: Wed, 21 Dec 2022 20:15:07 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: gdb
X-Bugzilla-Version: 7.11
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ariscop at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: OBSOLETE
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: resolution bug_status
Message-ID: <bug-20007-4717-nMn0EJTAQ4@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-20007-4717@http.sourceware.org/bugzilla/>
References: <bug-20007-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gdb-prs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D20007

Andrew Cook <ariscop at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |OBSOLETE
             Status|NEW                         |RESOLVED

--- Comment #4 from Andrew Cook <ariscop at gmail dot com> ---
Looking back i didn't explain this well at all

ntoskrnl has a base address of 0x400000 but is loaded at 0x80400000, unable=
 to
find any way to rebase a binary i resorted to manually mapping each section

But while 'info files' reported the sections at the correct address, symbols
were still located at the original address

reactos builds ntoskrnl with a base of 0x80400000 to work around the inabil=
ity
to rebase symbols, i was attempting to remove that workaround

if this was not user error and is a bug, and still present, it's likely nev=
er
going to be fixed anyway, so i'm closing it as obsolete

--=20
You are receiving this mail because:
You are on the CC list for the bug.=