Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: gdbserver/{<foo>,<os>,<bar>}.c?; Was: [rfa] gdbserver overhaul
Date: Fri, 27 Sep 2002 15:35:00 -0000	[thread overview]
Message-ID: <3BCDF237.8030609@cygnus.com> (raw)
In-Reply-To: <20011017164008.A15898@nevyn.them.org>


> Which part are you referring to?  The low-linux.c breakup?  I can do
> that; I can also test it on 80% of the affected targets, and I'd
> consider such a patch ``obvious''.

Yes the split.

Check the guideline for obvious. Your patch will knowingly break 
something.  Hmm, will someone object?

> I don't really see the point.  It's no more (in fact probably less)
> broken than all the other targets, which make the same or worse
> assumptions.  I'm trying to fix them, not delete them  [:)] I'm open to
> marking it obsolete, certainly.

The MIPS gbserver sim is very broken.  GDB has code to carefully map 
between a simulator and its internal register numbering.  It was 
originally added for the mips-gdb <-> sim interface.

>> With respect to sparc, if it really doesn't even build, then well, how 
>> motivated are you?  [:-)] You could fix it, obsolete it or transform it 
>> (still broken).
> 
> 
> For Solaris?  I'm not motivated in the slightest.  In fact, I'm tempted
> to mark all non-Linux gdbserver targets as obsolete, and repair them
> one at a time as volunteers, or at least testers, pop their heads up.

I don't think that is reasonable - it would be setting a precident for 
me doing things like ignoring / breaking currently working linux targets 
because (say) most are not multi-arch.

enjoy,
Andrew




  reply	other threads:[~2002-09-27 22:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-11 13:15 Daniel Jacobowitz
2001-10-14 18:13 ` Andrew Cagney
2001-10-14 18:44   ` Daniel Jacobowitz
2001-10-16 21:12     ` Andrew Cagney
2001-10-16 21:24       ` Daniel Jacobowitz
2001-10-16 21:09 ` Andrew Cagney
2001-10-16 21:23   ` Daniel Jacobowitz
2001-10-17  4:45     ` Eli Zaretskii
2001-10-17  9:06     ` Andrew Cagney
2001-10-17 10:57       ` Daniel Jacobowitz
2001-10-17 12:34     ` gdbserver/{<foo>,<os>,<bar>}.c?; Was: " Andrew Cagney
2001-10-17 13:39       ` Daniel Jacobowitz
2002-09-27 15:35         ` Andrew Cagney [this message]
2002-09-27 15:49           ` Andrew Cagney
2001-10-18  1:11       ` Eli Zaretskii
2001-10-18  9:30         ` Andrew Cagney
2001-10-18 12:36           ` Eli Zaretskii
2001-10-18 11:59             ` Andrew Cagney
2001-10-18 12:08               ` Daniel Jacobowitz
2001-10-21  4:02       ` Mark Kettenis
2001-10-21  9:15         ` Andrew Cagney
2001-10-17 15:17   ` Daniel Jacobowitz
2001-10-18 14:28     ` Andrew Cagney
2001-10-18 17:06       ` Daniel Jacobowitz

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=3BCDF237.8030609@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=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