Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: Patrick Monnerat <patrick@monnerat.net>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Add a timeout parameter to gdb_do_one_event
Date: Mon, 14 Mar 2022 16:17:44 +0000	[thread overview]
Message-ID: <8dda0fde-1dbf-256c-88bd-82910658857f@palves.net> (raw)
In-Reply-To: <20220314144927.172620-1-patrick@monnerat.net>

On 2022-03-14 14:49, Patrick Monnerat via Gdb-patches wrote:
> +      try
> +	{
> +	  if (mstimeout > 0)
> +	    timer_id = create_timer (mstimeout,
> +				     [] (gdb_client_data arg)
> +				     {
> +				       ((gdb::optional<int> *) arg)->reset ();
> +				     },
> +				     &timer_id);
> +	  res = gdb_wait_for_event (1);
> +	  if (timer_id.has_value ())
> +	    delete_timer (*timer_id);
> +	}
> +      catch (...)
> +	{
> +	  if (timer_id.has_value ())
> +	    delete_timer (*timer_id);
> +	  throw;
> +	}


Instead of duplicated code on normal and exception exits, you can use
a SCOPE_EXIT:

          gdb::optional<int> timer_id;

          SCOPE_EXIT 
            {
              if (timer_id.has_value ())
                delete_timer (*timer_id);
            };

	  if (mstimeout > 0)
	    timer_id = create_timer (mstimeout,
				     [] (gdb_client_data arg)
				     {
				       ((gdb::optional<int> *) arg)->reset ();
				     },
				     &timer_id);
	  return gdb_wait_for_event (1);


I think you don't even need the "res" variable this way.

  reply	other threads:[~2022-03-14 16:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14 14:49 Patrick Monnerat via Gdb-patches
2022-03-14 16:17 ` Pedro Alves [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-03-17 13:08 Patrick Monnerat via Gdb-patches
2022-04-15 16:21 ` Tom Tromey
2022-04-16  0:38   ` Patrick Monnerat via Gdb-patches
2022-07-22 13:41 ` Simon Marchi via Gdb-patches
2022-07-22 22:45   ` Patrick Monnerat via Gdb-patches
2022-07-25  1:07     ` Simon Marchi via Gdb-patches
2022-08-18 11:16 ` Andrew Burgess via Gdb-patches
2022-08-19 11:29   ` Patrick Monnerat via Gdb-patches
2022-08-23 18:38     ` Tom Tromey
2021-08-26 18:30 Patrick Monnerat via Gdb-patches
2021-08-23 18:23 Patrick Monnerat via Gdb-patches
2021-08-26  3:24 ` Simon Marchi via Gdb-patches
2021-08-26 11:36   ` Patrick Monnerat via Gdb-patches
2021-08-26 13:47     ` Simon Marchi via Gdb-patches
2021-08-26 15:14       ` Patrick Monnerat via Gdb-patches
2021-08-27 18:08     ` Tom Tromey
2021-08-28  0:07       ` Patrick Monnerat via Gdb-patches

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=8dda0fde-1dbf-256c-88bd-82910658857f@palves.net \
    --to=pedro@palves.net \
    --cc=gdb-patches@sourceware.org \
    --cc=patrick@monnerat.net \
    /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