Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Fix do_cleanups if oldchain is NULL
Date: Mon, 05 Jan 2004 15:32:00 -0000	[thread overview]
Message-ID: <3FF98396.3060700@gnu.org> (raw)
In-Reply-To: <20040102175138.GB11549@nevyn.them.org>

> 
> How about making NULL an internal error then, as below?  I think we
> should either do that or document its behavior, and it seems
> accident-prone.

I thought about that, and would likely be ok if there were only normal 
simple cleanups.  Its the "other" (i.e., final, run, exec, ...) cleanups 
that trouble me.

Andrew



  reply	other threads:[~2004-01-05 15:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-17 21:05 Jeff Johnston
2004-01-02 16:07 ` Andrew Cagney
2004-01-02 17:51   ` Daniel Jacobowitz
2004-01-05 15:32     ` Andrew Cagney [this message]
2004-01-05 15:36       ` Daniel Jacobowitz
2004-01-05 18:59   ` J. Johnston
2004-01-05 19:06     ` Daniel Jacobowitz
2004-01-05 21:18       ` J. Johnston

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=3FF98396.3060700@gnu.org \
    --to=cagney@gnu.org \
    --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