From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Status of external toolchain support
Date: Wed, 12 May 2010 21:34:41 +0000 (UTC) [thread overview]
Message-ID: <hsf6tg$9v9$1@dough.gmane.org> (raw)
In-Reply-To: 201005122319.35163.yann.morin.1998@anciens.enib.fr
On 2010-05-12, Yann E. MORIN <yann.morin.1998@anciens.enib.fr> wrote:
> The same entity shall build both the cross gdb and the gdbserver, as
> those two are tightly coupled, because of the protocol to exchange
> information between them.
Sorry, I don't understand where that limitation comes from.
The gdb remote protocol is standardized. It's plain ASCII, and I
can't see how it would be affected by the choice of toolchain. There
are plenty of third-party gdb servers that are not only built by
different entities, but the server isn't even built from gdb sources.
As long as as the gdb server and client versions are compatible (e.g.
they're using the same protocol) they should work fine.
Have you seen protocol failures betwee gdb server/client due to the
fact that a different toolchain was used to build them? If so, my
understand is that's a bug and should be reported to the gdb
maintainers.
--
Grant Edwards grant.b.edwards Yow! I invented skydiving
at in 1989!
gmail.com
next prev parent reply other threads:[~2010-05-12 21:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 17:15 [Buildroot] Status of external toolchain support Will Wagner
2010-05-12 21:19 ` Yann E. MORIN
2010-05-12 21:34 ` Grant Edwards [this message]
2010-05-12 21:53 ` Yann E. MORIN
2010-05-12 22:09 ` Grant Edwards
2010-05-12 21:36 ` Will Wagner
2010-05-12 21:47 ` Yann E. MORIN
2010-05-13 12:29 ` Mark Fisher
2010-05-13 15:22 ` Thomas Petazzoni
2010-05-13 17:21 ` Yann E. MORIN
2010-05-13 20:08 ` Thomas Petazzoni
2010-05-13 20:26 ` Yann E. MORIN
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='hsf6tg$9v9$1@dough.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=buildroot@busybox.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