Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Kevin Buettner <kevinb@cygnus.com>,
	Don Howard <dhoward@redhat.com>,
	gdb-patches@sources.redhat.com,
	Fernando Nasser <fnasser@redhat.com>,
	Michael Snyder <msnyder@cygnus.com>
Subject: Re: [RFA] deleting breakpoints inside of 'commands' [Repost]
Date: Wed, 26 Sep 2001 13:07:00 -0000	[thread overview]
Message-ID: <3BB2340C.CB386069@cygnus.com> (raw)
In-Reply-To: <3BAFE360.9080904@cygnus.com>

Andrew Cagney wrote:
> 
> >
> > I've looked your patch over, and it looks correct to me.  Having said
> > that, I think that the correctness of this patch is much less obvious
> > than the version that made a copy of the command chain associated with
> > a breakpoint.  I don't fault you for this; the changes in your current
> > patch are somewhat more distributed which means that there's more code
> > to consider (and more ways for something to get fouled up later on).
> 
> And guess what (sorry but this is funny :-) I suspect it does contain a
> bug.  Try:
> 
>         break main
>         commands
>         delete NN
>         leak-memory
>         end
> 
> The command ``leak-memory'' is invalid and will lead to an error() call
> and that will in turn long jump over the code that would free the list.
> 
> While the duplicate version contains the same bug, I suspect it is
> easier to fix vis:
> 
>         o       duplicate list
>         o       add list to a cleanup
>         o       run command
>         o       do cleanups
> 
> I suspect to do this with the non-duplicate version you'll need to add a
> catch_exceptions() call (nee catch_errors()) and check the state of that
> ->execute variable to figure out what to do.
> 

I don't see why it is not possible to register a cleanup in Don's latest
solution.  The function would do nothing unless a "delete NN" was executed
before we bail out.



> I do tend to agree with Kevin though.  Some times simplicity is best.
> 

I wish you have thought like that in previous instances. ;-)

And I don't think Don's latest patch is complex, or considerably more
complex than the simplistic copy approach (or hack!).  It is elegant 
(although Kevin's comments are valid and should be incorporated).



If Don can add a cleanup function and do the polishing suggested by Kevin
on his last patch I suggest that we stick with that one.


-- 
Fernando Nasser
Red Hat - Toronto                       E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9


  reply	other threads:[~2001-09-26 13:07 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0109211638230.1755-100000@theotherone>
2001-09-24 17:10 ` Kevin Buettner
2001-09-24 17:33   ` Kevin Buettner
2001-09-24 18:52   ` Andrew Cagney
2001-09-26 13:07     ` Fernando Nasser [this message]
2001-09-26 14:20       ` Kevin Buettner
2001-09-26 14:57         ` Fernando Nasser
2001-09-26 15:09           ` Andrew Cagney
2001-09-17  9:34 Don Howard
2001-09-17 15:39 ` Michael Snyder
2001-09-18  6:56   ` Fernando Nasser
2001-09-18  7:56     ` Andrew Cagney
2001-09-18  8:09       ` Fernando Nasser
2001-09-18 10:34       ` Michael Snyder
2001-09-18 17:47         ` Andrew Cagney
2001-09-18 18:03           ` Michael Snyder
2001-09-19  7:20             ` Fernando Nasser
2001-09-19  8:17               ` Andrew Cagney
2001-09-19  9:22                 ` Fernando Nasser
2001-09-19  9:33                 ` Don Howard
2001-09-19 12:08                   ` Kevin Buettner
2001-09-19 12:18                     ` Michael Snyder
2001-09-19 13:09                       ` Kevin Buettner
     [not found]                     ` <3BA905AD.5F8F1A68@redhat.com>
2001-09-19 14:22                       ` Kevin Buettner
2001-09-19 14:44                         ` Fernando Nasser
2001-09-20 15:24                 ` Don Howard
2001-09-20 18:05                   ` Andrew Cagney

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=3BB2340C.CB386069@cygnus.com \
    --to=fnasser@cygnus.com \
    --cc=ac131313@cygnus.com \
    --cc=dhoward@redhat.com \
    --cc=fnasser@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@cygnus.com \
    --cc=msnyder@cygnus.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