Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Greatwolf <gmane.greatwolf@mamber.net>
To: gdb@sources.redhat.com
Subject: i686-pc-mingw32 gdb: note executable format
Date: Sun, 17 Oct 2010 00:10:00 -0000	[thread overview]
Message-ID: <Xns9E13AE1AC10D8gmanegreatwolfmamber@80.91.229.10> (raw)

Hi,

I'm having an issue using gdb and I'm trying to track down the root cause 
of it. When debugging some executable files under this platform, gdb has 
trouble debugging certain executable formats. For example, try loading 
gdb notepad.exe under windows 7. gdb will give an error message:

  not in executable format: File format not recognized

Similarly, executables compiled and linked with digital mars C++ tools 
have the same problems as well as borland object files that are linked 
with the unilinker.exe. The demo program from pelib also fails to load 
under gdb. All in these cases gdb issues the same error message.

The error message of course doesn't make any sense, how could the binary 
not be a valid executable format?? The windows loader certainly has no 
issues loading and running it. Other debuggers and disassemblies have no 
problems opening/attaching to it.

On a similar note, using objdump on those above cases gives a similar 
error:

  File format not recognized

Any ideas what the issue might be? Note that in all cases I've checked to 
make sure I was't mixing 64-bit executes with 32-bit gdb and visa versa. 
I have a feeling it's probably an issue with binutils bfd.

Thanks


             reply	other threads:[~2010-10-17  0:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-17  0:10 Greatwolf [this message]
2010-10-23  8:29 ` Greatwolf
2010-10-23 10:00   ` Eli Zaretskii

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=Xns9E13AE1AC10D8gmanegreatwolfmamber@80.91.229.10 \
    --to=gmane.greatwolf@mamber.net \
    --cc=gdb@sources.redhat.com \
    /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