public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: Mohamed Bouhaouel <mohamed.bouhaouel@intel.com>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH 1/1] gdb, breakpoint: add a destructor to the watchpoint struct
Date: Tue, 04 Apr 2023 12:37:56 +0100	[thread overview]
Message-ID: <87ttxvc1yj.fsf@redhat.com> (raw)
In-Reply-To: <20230403145404.18548-1-mohamed.bouhaouel@intel.com>

Mohamed Bouhaouel via Gdb-patches <gdb-patches@sourceware.org> writes:

> Make sure to unlink the related breakpoint when the watchpoint instance
> is deleted.  This prevents having a wp-related breakpoint that is
> linked to a NULL watchpoint (e.g.  the watchpoint instance is being
> deleted when the 'watch' command fails).  With the below scenario,
> having such a left out breakpoint will lead to a GDB hang, and this
> is due to an infinite loop when deleting all inferior breakpoints.
>
> Scenario:
> 	(gdb) awatch <VAR>
> 	Target does not support this type of hardware watchpoint.
> 	(gdb) rwatch <VAR>
> 	Target does not support this type of hardware watchpoint.
> 	(gdb) <continue the program until the end>
> 	>> HANG <<
>

Is it not possible to create a test case based on this scenario?

Thanks,
Andrew

> Signed-off-by: Mohamed Bouhaouel <mohamed.bouhaouel@intel.com>
> ---
>  gdb/breakpoint.c | 15 +++++++++++++++
>  gdb/breakpoint.h |  3 +++
>  2 files changed, 18 insertions(+)
>
> diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
> index 7228acfd8fe..b9ddc85c30c 100644
> --- a/gdb/breakpoint.c
> +++ b/gdb/breakpoint.c
> @@ -9581,6 +9581,21 @@ break_range_command (const char *arg, int from_tty)
>    install_breakpoint (false, std::move (br), true);
>  }
>  
> +/* See breakpoint.h.  */
> +
> +watchpoint::~watchpoint ()
> +{
> +  /* Make sure to unlink the destroyed watchpoint from the related
> +     breakpoint ring.  */
> +
> +  breakpoint *bpt = this;
> +  breakpoint *related = bpt;
> +  while (related->related_breakpoint != bpt)
> +    related = related->related_breakpoint;
> +
> +  related->related_breakpoint = bpt->related_breakpoint;
> +}
> +
>  /*  Return non-zero if EXP is verified as constant.  Returned zero
>      means EXP is variable.  Also the constant detection may fail for
>      some constant expressions and in such case still falsely return
> diff --git a/gdb/breakpoint.h b/gdb/breakpoint.h
> index 7c5cf3f2bef..4f19e42dd83 100644
> --- a/gdb/breakpoint.h
> +++ b/gdb/breakpoint.h
> @@ -933,6 +933,9 @@ struct watchpoint : public breakpoint
>    void print_recreate (struct ui_file *fp) const override;
>    bool explains_signal (enum gdb_signal) override;
>  
> +  /* Destructor for WATCHPOINT.  */
> +  virtual ~watchpoint ();
> +
>    /* String form of exp to use for displaying to the user (malloc'd),
>       or NULL if none.  */
>    gdb::unique_xmalloc_ptr<char> exp_string;
> -- 
> 2.25.1
>
> Intel Deutschland GmbH
> Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
> Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
> Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva  
> Chairperson of the Supervisory Board: Nicole Lau
> Registered Office: Munich
> Commercial Register: Amtsgericht Muenchen HRB 186928


  reply	other threads:[~2023-04-04 11:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03 14:54 Mohamed Bouhaouel
2023-04-04 11:37 ` Andrew Burgess [this message]
2023-04-04 14:38   ` Bouhaouel, Mohamed
2023-04-04 16:29     ` Bouhaouel, Mohamed
2023-04-04 18:27 ` Tom Tromey

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=87ttxvc1yj.fsf@redhat.com \
    --to=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mohamed.bouhaouel@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).