From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] gdbserver 1/3 - top level config
Date: Wed, 06 Feb 2002 16:34:00 -0000 [thread overview]
Message-ID: <20020206193401.A20153@nevyn.them.org> (raw)
In-Reply-To: <20020205174549.A13231@nevyn.them.org>
On Tue, Feb 05, 2002 at 05:45:49PM -0500, Daniel Jacobowitz wrote:
> This is the first of three interdependent patches to revamp gdbserver.
> This first patch:
> - always builds gdbserver if it is configured
> - configures gdbserver only for Linux/{ARM,ia64,i386,m68k,mips,ppc,sh}.
>
> Those seven targets will hereafter be referred to as "The Seven",
> since I'm really tired of typing that list over and over :)
>
> This disables all the non-Linux targets, which I'm reasonably certain
> do not work. At least the NetBSD targets should be very easily
> reconstitutable. It also disables s390 and x86-64. That's just
> because I didn't have the necessary information handy for either, or a
> way to test either. I'll try to get those two fixed soon, as well as
> Sparc/Sparc64 which did not work at all.
>
> Actually, reading over this list, I believe that SH support is actually
> being contributed by this patch. I did it six or eight months ago, but
> in this new framework, so it couldn't be contributed before this.
>
> This patch contains only changes to top-level configury. OK to commit?
<nag>
For the curious, I ran the testsuite over gdbserver on i386-linux. Results:
=== gdb Summary ===
# of expected passes 6727
# of unexpected failures 980
# of unexpected successes 101
# of expected failures 102
# of unresolved testcases 11
# of untested testcases 6
# of unsupported tests 6
/opt/src/binutils/x86-as/gdb/testsuite/../../gdb/gdb version 2002-02-03-cvs -nx
That's after a patch to fix some timeout problems - checking [isnative]
instead of ![is_remote target] - which I'll post in a few days.
There's a LOT of timeouts. Including almost all of MI, for reasons not
immediately clear. And gcore failed to work over a remote link,
presumably because we lack some needed information that the remote
protocol can not supply. Ditto info proc.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-02-07 0:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 14:46 Daniel Jacobowitz
2002-02-06 16:34 ` Daniel Jacobowitz [this message]
2002-02-13 12:10 ` Daniel Jacobowitz
2002-02-13 20:20 ` Andrew Cagney
2002-02-13 21:32 ` Daniel Jacobowitz
2002-02-13 21:33 ` Andrew Cagney
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=20020206193401.A20153@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.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