This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
RE: binutils status ?
- From: "Ralf Habacker" <Ralf dot Habacker at freenet dot de>
- To: "Cygwin-Apps" <cygwin-apps at cygwin dot com>,"Binutils" <binutils at sources dot redhat dot com>
- Cc: "Nick Clifton" <nickc at cambridge dot redhat dot com>,"LaurentPinchart" <laurent dot pinchart at skynet dot be>
- Date: Thu, 23 May 2002 21:59:06 +0200
- Subject: RE: binutils status ?
Relating to this patch for peXXigen.c
bfd/peXXigen.c:
>date: 2002/05/15 15:28:12; author: nickc; state: Exp; lines: +54 -3
>Do not assume that the first thunk is located in the same section as the
>import table. Instead check, and if necessary load the section containing
>the thunk.
I have a question, which can perhaps answer anyone:
Does symbols, for which this patch is, are located in the text segment ?
The reason for this questioin is, because for auto-imported symbols the
first_thunk entry of the IMAGE_IMPORT_DESCRIPTOR points directly into the text
segment to a pointer and not(!) to an
IMAGE_IMPORT_BY_NAME structure, which lets the following codefragement crashes.
peXXigen.c::pe_print_idata()
<snip>
--- get IMAGE_IMPORT_BY_NAME structure values ----
ordinal = bfd_get_16 (abfd, data + iat_member - adj);
member_name = (char *) data + iat_member - adj + 2;
fprintf (file, "\t%04lx\t %4d %s\n",
(unsigned long) iat_member,
ordinal,
member_name);
}
Or does anyone another idea how to solve this ?
Ralf