From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: pedro@codesourcery.com (Pedro Alves)
Cc: gdb@sourceware.org, will_wagner@carallon.com (William Wagner)
Subject: Re: gdbserver 7.1 unable to read registers
Date: Thu, 07 Oct 2010 17:16:00 -0000 [thread overview]
Message-ID: <201010071716.o97HGANJ009653@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <201009241539.35561.pedro@codesourcery.com> from "Pedro Alves" at Sep 24, 2010 03:39:35 PM
Pedro Alves wrote:
> On Friday 24 September 2010 15:05:11, Ulrich Weigand wrote:
> > As we have more and more platforms where gdbserver simply will not work
> > correctly without XML support, maybe we should make --with-expat the
> > default mode at some point in time? Users would still be able to
> > build with --without-expat if they really want to ...
>
> I guess. Most native targets don't need it though.
OK, I see.
> On the other hand, there's scope for improvement in those warnings.
> It's not surprising that users don't know the consequences of not
> being able to parse a "XML target description" are. Making
> those clearer in terms of consequences would probably already go a long way
> in avoiding surprises. Something along the lines of:
>
> "Can not parse XML target description; XML support was disabled at compile time. "
> "GDB may not be able to read registers correctly."
This would certainly be helpful.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
prev parent reply other threads:[~2010-10-07 17:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 17:17 William Wagner
2010-09-24 7:47 ` Jan Kratochvil
2010-09-24 7:54 ` William Wagner
2010-09-24 13:30 ` Jon Smirl
2010-09-24 12:58 ` Ulrich Weigand
2010-09-24 13:36 ` Pedro Alves
2010-09-24 13:44 ` William Wagner
2010-09-24 14:05 ` Ulrich Weigand
2010-09-24 14:39 ` Pedro Alves
2010-09-27 10:25 ` Steffen Dettmer
2010-09-27 14:44 ` Daniel Jacobowitz
2010-10-07 17:16 ` Ulrich Weigand [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=201010071716.o97HGANJ009653@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=will_wagner@carallon.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