Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dan@cgsoftware.com>
To: jtc@redback.com
Cc: Daniel Berlin <dan@cgsoftware.com>,
	RDBrown@mira.net, RodneyBrown@mynd.com,
	gdb-patches@sources.redhat.com
Subject: Re: PATCH: gdb/corefile.c (0401 snap on HP-UX).
Date: Tue, 10 Apr 2001 21:06:00 -0000	[thread overview]
Message-ID: <m2k84s3wt1.fsf@dynamic-addr-83-177.resnet.rochester.edu> (raw)
In-Reply-To: <5mwv8s8diu.fsf@jtc.redback.com>

jtc@redback.com (J.T. Conklin) writes:

> >>>>> "Daniel" == Daniel Berlin <dan@cgsoftware.com> writes:
> >> I'm not sure that I like this patch, but I'm not sure I can come up
> >> with a resonable alternative in the short term.  Perhaps the code to
> >> find the symbol file cooresponding to the core file (this is the bit
> >> that needs symfile_objfile) should be replaced with a config specific
> >> hook.  But because it is also wrapped with HPUXHPPA, I'm not opposed
> >> to checking this in now, and fixing it up later.
> 
> Dan> Please don't.
> 
> See my response to Kevin.  In short, I'm not going to.
> 
Just got it. 
> Dan> The idea is not to *add* things wrapped with HPUXHPPA, rather,
> Dan> remove them.  Pretending they will be fixed up later isn't a
> Dan> good idea. They haven't been thus far. There is no indication
> Dan> this will change.
> 
> You don't need to lecture me about this.  
Okey dokey, sorry about that.
> I've been one of the most
> vocal critics about adding cruft believing the fiction we'll fix it
> later. 

It's not just cruft, too, as i'm sure you know.  There are whole
targets and language support modules that never got fixed "later".
:)


>  This is why I asked for further comments instead of commit-
>  ing the patch as is.  
> 
>         --jtc
> 
> -- 
> J.T. Conklin
> RedBack Networks

-- 
I was going to tape some records onto a cassette, but I got the
wires backwards.  I erased all of the records.  When I returned
them to my friend, he said, "Hey, these records are all blank."


      reply	other threads:[~2001-04-10 21:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-09  6:03 RDBrown
2001-04-09 10:17 ` Kevin Buettner
2001-04-10 17:46   ` J.T. Conklin
2001-04-12  9:40     ` J.T. Conklin
2001-04-09 10:24 ` J.T. Conklin
2001-04-10 16:14   ` Daniel Berlin
2001-04-10 17:51     ` J.T. Conklin
2001-04-10 21:06       ` Daniel Berlin [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=m2k84s3wt1.fsf@dynamic-addr-83-177.resnet.rochester.edu \
    --to=dan@cgsoftware.com \
    --cc=RDBrown@mira.net \
    --cc=RodneyBrown@mynd.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jtc@redback.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