This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA] gdbserver 1/3 - top level config
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: gdb-patches at sources dot redhat dot com
- Date: Wed, 6 Feb 2002 19:34:01 -0500
- Subject: Re: [RFA] gdbserver 1/3 - top level config
- References: <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