From: Chris Sutcliffe <ir0nh34d@gmail.com>
To: gdb@sourceware.org
Subject: Re: Cross debugger
Date: Thu, 16 Jun 2011 11:54:00 -0000 [thread overview]
Message-ID: <BANLkTim=5WV+shf2sZPczeAJt=HQFttPrA@mail.gmail.com> (raw)
In-Reply-To: <20110616025342.GS5944@adacore.com>
On 15 June 2011 22:53, Joel Brobecker wrote:
> What I don't understand is why you created a cross compiler/debugger,
> while it seems to me you could have just created a native x64 MinGW
> toolset. That's what we do at AdaCore: We use cygwin as the build
> environment, but then build a MinGW toolset by configuring with
> --build=x86_64-pc-mingw32. As far as I know, the gdbserver will
> be automatically built.
Good point, for some reason I was thinking that since gdb would be
running withing the Cygwin environment I would need the
'--host=i686-pc-cygwin'. If I build a native x64 MinGW gdb will it
understand Cygwin paths correctly?
>> (gdb) start
> [...]
>> Don't know how to run. Try "help target".
>
> And that's also expected, since you have a cross-debugger. So the
> debugger is expecting you to connect to the target where the process
> is running.
Ah, I didn't realize a cross-debugger could only be used to connect to
running process.
> But the nice thing is that, if I understand your situation correctly,
> as soon as you build a native debugger, you will not have to worry
> about that anymore.
Indeed, I hope so.
Thank you,
Chris
--
Chris Sutcliffe
http://emergedesktop.org
http://www.google.com/profiles/ir0nh34d
next prev parent reply other threads:[~2011-06-16 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 2:00 Chris Sutcliffe
2011-06-16 2:54 ` Joel Brobecker
2011-06-16 11:54 ` Chris Sutcliffe [this message]
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='BANLkTim=5WV+shf2sZPczeAJt=HQFttPrA@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).