Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com, nick@duffek.com
Subject: Re: [PATCH RFC] AIX thread support
Date: Sat, 13 Jul 2002 17:25:00 -0000	[thread overview]
Message-ID: <3D30BD5F.6050205@ges.redhat.com> (raw)
In-Reply-To: <1020713011530.ZM10495@localhost.localdomain>

> [...]
> 
>> A quick glance suggests a review is needed.   For instance, from a 
>> coding (not thread -> MichaelS) viewpoint ``#define DEBUG 0'' should be 
>> handled at run-time and should be written to ``gdb_stdlog''.  If 
>> anything, perhaphs like for ada, this file could be initially commited, 
>> but not actually included/enabled.  That should at least make the review 
>> process easier.
> 
> 
> As suggested, I've commited aix-thread.c to make the review process
> easier.
> 
> Keep in mind that aix-thread.c will only be used for native AIX
> builds.  As such, I think the criteria for including/enabling this
> code should be much lower than that for core code or even target
> specific code.

No.

Past history teaches us that once code is in and enabled it is very 
unlikely to be cleaned up or fixed.  Instead the problematic aspects 
tend to be copied leading to a gradual spread.

#define DEBUG is, itself, an example of this problem.  The idea was 
likely (and unfortunatly) picked up from one of the other older modules 
that still uses that and similar techniques.

Andrew



      reply	other threads:[~2002-07-13 23:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-12 12:46 Kevin Buettner
2002-07-12 16:12 ` Andrew Cagney
2002-07-13  5:25   ` Kevin Buettner
2002-07-13 17:25     ` Andrew Cagney [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=3D30BD5F.6050205@ges.redhat.com \
    --to=ac131313@ges.redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@redhat.com \
    --cc=nick@duffek.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