Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Fix do_cleanups if oldchain is NULL
Date: Fri, 02 Jan 2004 17:51:00 -0000	[thread overview]
Message-ID: <20040102175138.GB11549@nevyn.them.org> (raw)
In-Reply-To: <3FF59719.7020908@gnu.org>

On Fri, Jan 02, 2004 at 11:06:49AM -0500, Andrew Cagney wrote:
> >I recently solved a bug on the ia64 concerning cleanups.  What was 
> >happening was that a cleanup list was being re-initialized to NULL inside 
> >a loop and later do_cleanups() was called.  This caused the entire cleanup 
> >list to be run because the design is to run the list until the passed in 
> >cleanup is reached.  This caused other errors when the stream being used 
> >was deleted, etc...
> >
> >This patch adds a check to do_my_cleanups() so no cleanups will be 
> >performed if the passed in chain is NULL.
> >
> >Ok to commit?
> 
> (hmm, no one thought to review this while I was on hols :-()

Sorry, I was holding off on reviewing other people's patches during my vacation
so that I could catch up on my own.

> I think the bug is in the calling code, and not utils.c.  That patch 
> unfortunatly makes a fundamental change to the core of the cleanup code 
> and there's no easy way of demonstrating that other callers aren't 
> assuming that NULL implies do all cleanups.

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.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

2003-01-02  Daniel Jacobowitz  <drow@mvista.com>

	* utils.c (do_my_cleanups): Raise an internal error if the old_chain
	is NULL.

Index: utils.c
===================================================================
RCS file: /cvs/src/src/gdb/utils.c,v
retrieving revision 1.111
diff -u -p -r1.111 utils.c
--- utils.c	2 Jan 2004 17:35:01 -0000	1.111
+++ utils.c	2 Jan 2004 17:49:37 -0000
@@ -1,8 +1,8 @@
 /* General utility routines for GDB, the GNU debugger.
 
    Copyright 1986, 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995,
-   1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003 Free Software
-   Foundation, Inc.
+   1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004
+   Free Software Foundation, Inc.
 
    This file is part of GDB.
 
@@ -318,6 +318,11 @@ do_my_cleanups (struct cleanup **pmy_cha
 		struct cleanup *old_chain)
 {
   struct cleanup *ptr;
+
+  if (old_chain == NULL)
+    internal_error (__FILE__, __LINE__,
+		    "NULL chain passed to do_my_cleanups");
+
   while ((ptr = *pmy_chain) != old_chain)
     {
       *pmy_chain = ptr->next;	/* Do this first incase recursion */


  reply	other threads:[~2004-01-02 17:51 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 [this message]
2004-01-05 15:32     ` Andrew Cagney
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=20040102175138.GB11549@nevyn.them.org \
    --to=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