From: Eli Zaretskii <eliz@gnu.org>
To: Greatwolf <gmane.greatwolf@mamber.net>
Cc: gdb@sources.redhat.com
Subject: Re: i686-pc-mingw32 gdb: note executable format
Date: Sat, 23 Oct 2010 10:00:00 -0000 [thread overview]
Message-ID: <8362wt8c01.fsf@gnu.org> (raw)
In-Reply-To: <Xns9E1AF3C41B7Bgmanegreatwolfmamber@80.91.229.10>
> From: Greatwolf <gmane.greatwolf@mamber.net>
> Date: Sat, 23 Oct 2010 08:29:35 +0000 (UTC)
>
>
> Does anyone have any thoughts on what the problem might be? How can I start
> debugging this issue?
Put a breakpoint on the code that issues the error message, then work
up the call stack to see the reason.
It sounds like some variant(s) of pe-coff executable format are not
recognized, but without specific details it will be impossible to find
the proper solution.
prev parent reply other threads:[~2010-10-23 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 0:10 Greatwolf
2010-10-23 8:29 ` Greatwolf
2010-10-23 10:00 ` Eli Zaretskii [this message]
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=8362wt8c01.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=gmane.greatwolf@mamber.net \
/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