From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Kai Tietz'" <Kai.Tietz@onevision.com>,
"'Joel Brobecker'" <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [patch] Reading coff-pe-read files
Date: Wed, 07 Jan 2009 13:54:00 -0000 [thread overview]
Message-ID: <004101c970cf$5ee27390$1ca75ab0$@u-strasbg.fr> (raw)
In-Reply-To: <OFB1459990.B6D7FE2C-ONC1257537.0046DD2E-C1257537.0048CC7E@onevision.de>
Should this be transformed so that we can also
correctly cross-read 64-bit PE files
on 32-bit and vice-versa?
Possibly by defining an extra offset
that would be set to 16 if target is "pe-x86-64" or "pei-x86-64"
and to zero otherwise?
Pierre Muller
Pascal language support maintainer for GDB
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Kai Tietz
> Envoyé : Wednesday, January 07, 2009 2:15 PM
> À : Joel Brobecker
> Cc : gdb-patches@sourceware.org
> Objet : [patch] Reading coff-pe-read files
>
> Hi,
>
> One small piece for x86_64 windows support in coff-pe-read.c seems to
> be missing. In function read_pe_exported_syms wrong indexes are used to
> find exports of the image.
> The source uses here the same pattern as in bfd/pe-dll.c.
>
> ChangeLog
>
> 2009-01-07 Kai Tietz <kai.tietz@onevision.com>
>
> * coff-pe-read.c (read_pe_exported_syms): Enable read of PE+
> export directory.
>
>
> I am uncertain, which macro I should use here (or if it would be better
> to
> make for PE+ a copy of this file), so I used _WIN64 as condition.
>
> Cheers,
> Kai
>
> PS: I have already papers ready with FSF for gdb, so there shouldn't be
> any problem about taking parts of my donated code, I've provided to
> Joel
> IMHO.
>
>
>
> | (\_/) This is Bunny. Copy and paste Bunny
> | (='.'=) into your signature to help him gain
> | (")_(") world domination.
next prev parent reply other threads:[~2009-01-07 13:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 12:27 [RFA/commit] arch-utils.c: Use host_address_to_string when printing function addresses Joel Brobecker
2009-01-07 13:15 ` [patch] Reading coff-pe-read files Kai Tietz
2009-01-07 13:54 ` Pierre Muller [this message]
2009-01-09 11:09 ` [RFA/commit] arch-utils.c: Use host_address_to_string when printing function addresses Joel Brobecker
2009-01-07 13:51 [patch] Reading coff-pe-read files Kai Tietz
2009-01-08 9:53 ` Joel Brobecker
2009-01-08 10:23 ` Kai Tietz
2009-01-08 11:10 ` Joel Brobecker
2009-01-08 12:53 ` Kai Tietz
2009-01-08 12:58 ` Joel Brobecker
2009-01-08 13:09 ` Joel Brobecker
2009-01-08 13:37 ` Kai Tietz
2009-01-08 20:07 ` Christopher Faylor
2009-01-08 20:55 ` Kai Tietz
2009-01-09 8:58 ` Pedro Alves
2009-01-09 9:33 ` Kai Tietz
2009-01-08 10:36 ` Pierre Muller
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='004101c970cf$5ee27390$1ca75ab0$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=Kai.Tietz@onevision.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@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