This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
> > I found a bug in pe_print_idata. In some PE files (namely drivers) > > the 'first thunk' is not located in the same section as the import > > table itself. This leads to weird behaviours, and segfaults. > An additional example for this is the auto-import stuff. IMAGE_IMPORT_DESCRIPTORS with auto-imported data points to an IAT entry in the text segment. This let objdump crash, which I have fixed in http://sources.redhat.com/ml/binutils/2002-04/msg00415.html. I think Laurent have fixed this bug in a general way, because I have only avoided the segfault in this specific case. > Is there a simple way to reproduce this problem ? For Auto-import build a dll with data variables, create an app which reference to this data and do a objdump -x client.exe let objdump crashes. > Ideally I would like a test that could be added to the test suite, but if this is not > feasible then some instructions on how to reproduce the failure would > be helpful. See the appended testcase. Perhaps this helps. Ralf
Attachment:
package.tar.bz2
Description: Binary data
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |