Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
	mark.kettenis@xs4all.nl, joseph@codesourcery.com,
	kevinb@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: Assume solib.h
Date: Tue, 16 Nov 2004 01:20:00 -0000	[thread overview]
Message-ID: <20041116012035.GA31575@nevyn.them.org> (raw)
In-Reply-To: <419942CB.4000905@gnu.org>

On Mon, Nov 15, 2004 at 06:59:07PM -0500, Andrew Cagney wrote:
> 
> >I'm with Mark on this one: a patch that potentially breaks a supported
> >platform doesn't get my vote.  If a platform is supported, it deserves
> >that we don't break it, and calling it ``marginal'' doesn't change
> >anything.
> 
> Eli, can you perhaphs explain what exactly you mean by "supported", how 
> the GNU project benefits by expending already limited resources on 
> continually fixing vax-ultrix - a non GNU system, and how my change 
> breaks it?

Mark wrote:

>please don't check in something like this without testing                                              
>this on some sort of embedded target, vax-dec-openbsd* or                                              
>vax-dec-ultrix4*.                                                                                      

Vax is by no means an embedded target, so I think his meaning is fairly
clear - it's a sample target on which GDB does not support shared
libraries.  Please don't try to change the subject by fixating on the
Vax.

Could you explain what _you_ mean by supported?  My interpretation is
that a platform on which GDB works, deliberately by included code
rather than accidentally through support for some other platform, is
obviously "supported".  We've gone to some effort to add the support
and breaking it is a disservice to our users.

-- 
Daniel Jacobowitz


  reply	other threads:[~2004-11-16  1:20 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-11 19:39 Andrew Cagney
2004-11-11 20:06 ` Mark Kettenis
2004-11-11 21:48   ` Andrew Cagney
2004-11-11 22:24     ` Mark Kettenis
2004-11-12 15:52       ` Andrew Cagney
2004-11-12 17:20         ` Eli Zaretskii
2004-11-15 21:32           ` Kevin Buettner
2004-11-15 23:35             ` Mark Kettenis
2004-11-17 17:35             ` Eli Zaretskii
2004-11-15 23:59           ` Andrew Cagney
2004-11-16  1:20             ` Daniel Jacobowitz [this message]
2004-11-16  5:00             ` Eli Zaretskii
2004-11-16  8:37               ` Mark Kettenis
2004-11-16 20:54                 ` Eli Zaretskii
2004-11-16 16:14               ` Andrew Cagney
2004-11-16 19:18                 ` Mark Kettenis
2004-11-18 14:10                   ` Andrew Cagney
2004-11-18 14:37                     ` Mark Kettenis
2004-11-18 17:28                       ` Kevin Buettner
2004-11-19 17:11                       ` Andrew Cagney
2004-11-19 17:25                         ` Randolph Chung
2004-11-19 17:36                           ` Joel Brobecker
2004-11-19 17:40                             ` Randolph Chung
2004-11-19 17:56                               ` Joel Brobecker
2004-11-19 19:29                         ` Joseph S. Myers
2004-11-16 21:06                 ` Eli Zaretskii
2004-11-16 22:27                   ` Andrew Cagney
2004-11-17  4:52                     ` Eli Zaretskii
2004-11-16  1:40         ` Daniel Jacobowitz
2004-11-16  4:54           ` Eli Zaretskii
2004-11-16 16:31           ` Andrew Cagney
2004-11-16 19:45             ` Mark Kettenis
2004-11-16 21:06             ` Eli Zaretskii
2004-11-12  1:11 ` Randolph Chung
2004-11-13  1:10   ` 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=20041116012035.GA31575@nevyn.them.org \
    --to=drow@false.org \
    --cc=cagney@gnu.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=kevinb@redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    /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