Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Chastain <mec.gnu@mindspring.com>
To: pgilliam@us.ibm.com, gdb-patches@sources.redhat.com
Cc: cagney@gnu.org
Subject: Re: [PATCH] Fixes testsuit/gdb.base/annota1.exp
Date: Thu, 23 Sep 2004 17:25:00 -0000	[thread overview]
Message-ID: <415300BA.nail1Q01VH9OJ@mindspring.com> (raw)
In-Reply-To: <200409221910.41605.pgilliam@us.ibm.com>

This is good work.  Here's my nit-picking.  The main issue is
generating backtrace.c versus a static file.

Michael

. ChangeLog entry

. Drop the "Please email any bugs, comments, ..." inside the file.

. It's elegant to generate the C program, but there are a couple of
  problems.  You're writing on the source tree which screws up people
  who run multiple test runs out of the same source tree simultaneously.
  And all the external calls need error checking.  And there is a
  copyright notice in backtrace.c, but no license.

  Just drop the generation and supply backtrace.c like a normal file.
  That loses the ability to change subr_depth easily, but that's okay.

. subr_depth is still cool, you just have to document that it has to
  match backtrace.c.


  parent reply	other threads:[~2004-09-23 17:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-21 21:43 Paul Gilliam
2004-09-22 14:01 ` Andrew Cagney
2004-09-22 16:56   ` Paul Gilliam
2004-09-22 19:54     ` Andrew Cagney
2004-09-23  2:13       ` Paul Gilliam
2004-09-23 17:08         ` Michael Chastain
2004-09-23 17:25         ` Michael Chastain [this message]
2004-09-24 22:38         ` Test "set backtrace ..."; " Andrew Cagney
2004-09-23 17:25 ` Michael Chastain
2005-04-07 17:27 Paul Gilliam
2005-04-14 19:36 ` Daniel Jacobowitz
2005-04-15 23:38   ` Paul Gilliam
2005-04-27 15:49     ` Daniel Jacobowitz
2005-04-27 20:02       ` Paul Gilliam

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=415300BA.nail1Q01VH9OJ@mindspring.com \
    --to=mec.gnu@mindspring.com \
    --cc=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=pgilliam@us.ibm.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