From: Chris Sutcliffe <ir0nh34d@gmail.com>
To: gdb@sourceware.org
Subject: Cross debugger
Date: Thu, 16 Jun 2011 02:00:00 -0000 [thread overview]
Message-ID: <BANLkTikzf18uc-yO4ehRBxPPyNqYnDFnRQ@mail.gmail.com> (raw)
Hi All,
I'm trying to debug a binary I made using the x86_64-w64-mingw32 cross
compiler toolchain hosted on Cygwin. To that end I've attempted to
create an x86_64-w64-mingw32 cross debugger by specifying
'--target=x86_64-w64-mingw32' when configuring gdb 7.2. It worked in
that a gdb.exe and gdbtui.exe were created (thought there was no
gdbserver.exe created). I was off to a great start, in that this
cross debugger was able to load the 64-bit binary, find the symbols
and I was even able to set break points. I then tried to start the
executable and that's where I hit the wall. I couldn't get gdb to run
the executable:
(gdb) start
Temporary breakpoint 2 at 0x40f2e0: file
/home/user/mingw64/mingw64-x86_64-runtime-1.0b_svn4075-1/src/mingw-w64-crt/crt/crt0_c.c,
line 17.
Starting program: /usr/src/emerge/experimental/Source/bin64/emergeLauncher.exe
Don't know how to run. Try "help target".
I'm running this on a 64-bit Win7 machine, so I would assume it should
know how to run it. Did I miss something when creating this cross
debugger?
Thank you,
Chris
--
Chris Sutcliffe
http://emergedesktop.org
http://www.google.com/profiles/ir0nh34d
next reply other threads:[~2011-06-16 2:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 2:00 Chris Sutcliffe [this message]
2011-06-16 2:54 ` Joel Brobecker
2011-06-16 11:54 ` Chris Sutcliffe
2011-06-16 13:54 ` Paul Koning
2011-06-16 14:19 ` Pedro Alves
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=BANLkTikzf18uc-yO4ehRBxPPyNqYnDFnRQ@mail.gmail.com \
--to=ir0nh34d@gmail.com \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).