Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Don Howard <dhoward@redhat.com>
Cc: Joel Brobecker <brobecker@gnat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] GDB/622 - clear current breakpoint in commands causestrouble
Date: Sat, 24 Aug 2002 02:17:00 -0000	[thread overview]
Message-ID: <3D66D9D9.8628BDF@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0208221506430.11494-100000@theotherone.redhat-remotie.org>

[-- Attachment #1: Type: text/plain, Size: 1429 bytes --]

Don Howard wrote:
> 
> On Thu, 22 Aug 2002, Michael Snyder wrote:
> 
> > Joel Brobecker wrote:
>
> > > > 2002-07-31  Joel Brobecker  <brobecker@gnat.com>
> > > >
> > > >         * cli/cli-scripts.c (copy_command_lines): New function.
> > > >         (make_cleanup_free_command_lines): Make this function non static.
> > > >
> > > >         * defs.h (copy_command_lines): Add definition.
> > > >         (make_cleanup_free_command_lines): Add definition.
> > > >
> > > >         * breakpoint.c (bpstat_do_actions): Execute a temporary copy of
> > > >         the command-list associated to each breakpoint hit, in order to
> > > >         avoid accessing a dangling pointer, in case one of the commands
> > > >         in the list causes the breakpoint to be deleted.
>
> > It looks OK to me, but I'd like to run it by Don Howard,
> > who has looked at this before.  Don, this patch looks a lot
> > simpler than the one you submitted (which, I think, died on
> > the vine (mea culpa)).  Do you think it will do the job?
>
> Yes this patch looks very much like one of my earlier attempts.  Joel's
> copy_command_lines() is simpler and catches a few bugs that I noticed in
> my implementation.  One question: is it important to use xstrdup() over
> plain strdup()?
> 
> You already pointed out the cleanup issues.  Once that is corrected, I'd
> recomend it.

Joel, Don, 

What do you think of the attached, to fix the cleanup issue?

[-- Attachment #2: joel1a.diff --]
[-- Type: text/plain, Size: 1429 bytes --]

Index: breakpoint.c
===================================================================
RCS file: /cvs/src/src/gdb/breakpoint.c,v
retrieving revision 1.82
diff -p -r1.82 breakpoint.c
*** breakpoint.c	23 Aug 2002 20:49:38 -0000	1.82
--- breakpoint.c	23 Aug 2002 23:47:18 -0000
*************** top:
*** 1927,1933 ****
    breakpoint_proceeded = 0;
    for (; bs != NULL; bs = bs->next)
      {
!       cmd = bs->commands;
        while (cmd != NULL)
  	{
  	  execute_control_command (cmd);
--- 1927,1939 ----
    breakpoint_proceeded = 0;
    for (; bs != NULL; bs = bs->next)
      {
!       struct cleanup *copy_cleanup;
! 
!       /* Use a temporary copy of the commands, as one command in the list
!          may cause this breakpoint and its commands to be deleted.  */
!       cmd = copy_command_lines (bs->commands);
!       copy_cleanup = make_cleanup_free_command_lines (&cmd);
! 
        while (cmd != NULL)
  	{
  	  execute_control_command (cmd);
*************** top:
*** 1945,1954 ****
  	goto top;
        else
  	bs->commands = NULL;
-     }
  
!   executing_breakpoint_commands = 0;
!   discard_cleanups (old_chain);
  }
  
  /* This is the normal print function for a bpstat.  In the future,
--- 1951,1960 ----
  	goto top;
        else
  	bs->commands = NULL;
  
!       do_cleanups (copy_cleanup);
!     }
!   do_cleanups (old_chain);
  }
  
  /* This is the normal print function for a bpstat.  In the future,

  reply	other threads:[~2002-08-24  0:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-31 13:09 [RFA] GDB/622 - clear current breakpoint in commands causes trouble Joel Brobecker
2002-08-20  6:27 ` Joel Brobecker
2002-08-22 15:01   ` Michael Snyder
2002-08-23 11:12     ` Don Howard
2002-08-24  2:17       ` Michael Snyder [this message]
2002-08-26 15:31       ` Kevin Buettner
2002-08-27 15:28         ` Andrew Cagney
2002-08-22 18:53 ` Michael Snyder

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=3D66D9D9.8628BDF@redhat.com \
    --to=msnyder@redhat.com \
    --cc=brobecker@gnat.com \
    --cc=dhoward@redhat.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