public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-20007-4717-nMn0EJTAQ4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20007-4717@http.sourceware.org/bugzilla/>

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

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 inability
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 never
going to be fixed anyway, so i'm closing it as obsolete

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

           reply	other threads:[~2022-12-21 20:15 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-20007-4717@http.sourceware.org/bugzilla/>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-20007-4717-nMn0EJTAQ4@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).