From: Joel Brobecker <brobecker@gnat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] GDB/624 - tbreak commands not executed when breakpoint hit
Date: Tue, 20 Aug 2002 06:28:00 -0000 [thread overview]
Message-ID: <20020820132818.GE25997@gnat.com> (raw)
In-Reply-To: <20020731200936.GL683@gnat.com>
ping?
> 2002-07-31 Joel Brobecker <brobecker@gnat.com>
>
> * breakpoint.c (breakpoint_auto_delete): Do not delete temporary
> breakpoints to which a list of commands is attached. Mark them
> for deletion at the next stop instead. Also disable them to avoid
> hitting these breakpoints again.
> Move the part that deletes the to-be-deleted breakpoints before
> the part that deletes the temporary breakpoints, to avoid immediately
> deleting the temporary breakpoints that we just marked for deletion.
>
> 2002-07-31 Joel Brobecker <brobecker@gnat.com>
>
> * gdb.base/commands.exp (temporary_breakpoint_commands): New test.
--
Joel
next prev parent reply other threads:[~2002-08-20 13:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 13:14 Joel Brobecker
2002-07-31 13:16 ` Joel Brobecker
2002-08-20 6:28 ` Joel Brobecker [this message]
2002-08-22 15:10 ` Michael Snyder
2002-08-22 15:31 ` Joel Brobecker
2002-08-22 18:37 ` Michael Snyder
2002-09-27 16:10 ` 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=20020820132818.GE25997@gnat.com \
--to=brobecker@gnat.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