public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug win32/12716] addresses of exported symbols of a DLL should be looked up by ordinal
Date: Sat, 11 Feb 2023 22:07:38 +0000	[thread overview]
Message-ID: <bug-12716-4717-GYv3HwLlBq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12716-4717@http.sourceware.org/bugzilla/>

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

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark at klomp dot org

--- Comment #6 from Mark Wielaard <mark at klomp dot org> ---
I can confirm that your paperwork is on file.
You submitted the patch and it was reviewed in this thread:
https://inbox.sourceware.org/gdb-patches/1307879815.1831.0.camel@t41.thuisdomein/

And it looks like something similar to (or inspired on) your patch was
committed as part of:

commit 3999122f0c8766df3a55462df626d607ebe5a735
Author: Pierre Muller <muller@sourceware.org>
Date:   Thu Dec 13 10:44:45 2012 +0000

            * coff-pe-read.h (pe_text_section_offset): Declare new function.
            * coff-pe-read.c (debug_coff_pe_read): New static variable.
            (struct read_pe_section_data): Add section_name field.
            (IMAGE_SCN_CNT_CODE): New macro, if not already defined.
            (IMAGE_SCN_CNT_INITIALIZED_DATA): Ditto.
            (IMAGE_SCN_CNT_UNINITIALIZED_DATA): Ditto.
            (get_pe_section_index): New function.
            (struct pe_sections_info): New type.
            (get_section_vmas): Use new struct pe_sections_info.
            (add_pe_exported_sym): Handle unnamed exported function.
            (add_pe_forwarded_sym): New function.
            (read_pe_truncate_name): Truncate at last dot.
            (pe_as16): New function.
            (read_pe_exported_syms): Use ordinal of function to
            retrieve correct RVA address of function and handle
            forwarded symbol.
            (pe_text_section_offset): New function.
            (show_debug_coff_pe_read): New function.
            (_initialize_coff_pe_read): New function adding
            'set/show debug coff_pe_read' commands.

            * windows-tdep.c (windows_xfer_shared_library): Use
            pe_text_section_offset function instead of possibly wrong
            0x1000 constant for .text sextion offset.

Which has a very long thread discussing it:
https://inbox.sourceware.org/gdb-patches/006001cdaada$00c81f00$02585d00$@muller@ics-cnrs.unistra.fr/t/#u

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

  parent reply	other threads:[~2023-02-11 22:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29 19:20 [Bug win32/12716] New: " pebolle at tiscali dot nl
2011-04-30 20:39 ` [Bug win32/12716] " pebolle at tiscali dot nl
2011-06-11 13:32 ` pebolle at tiscali dot nl
2011-06-12  3:50 ` qiyao at gcc dot gnu.org
2023-02-11 17:59 ` tromey at sourceware dot org
2023-02-11 19:42 ` pebolle at tiscali dot nl
2023-02-11 22:07 ` mark at klomp dot org [this message]
2023-02-11 23:10 ` tromey at sourceware dot org

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-12716-4717-GYv3HwLlBq@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).