From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH 7/7] gdbserver: remove support for ARM/WinCE
Date: Thu, 14 May 2020 13:30:49 -0700 [thread overview]
Message-ID: <20200514133049.2297a58a@f31-4.lan> (raw)
In-Reply-To: <20200514190537.2321826-8-simon.marchi@efficios.com>
Hi Simon,
Just one nit, maybe...
On Thu, 14 May 2020 15:05:37 -0400
Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> wrote:
> diff --git a/gdbserver/win32-low.cc b/gdbserver/win32-low.cc
> index 4eb63b7ca25a..d671691a575d 100644
> --- a/gdbserver/win32-low.cc
> +++ b/gdbserver/win32-low.cc
> @@ -1414,69 +1414,39 @@ get_child_debug_event (DWORD *continue_status,
> goto gotevent;
> }
>
> -#ifndef _WIN32_WCE
> attaching = 0;
> -#else
> - if (attaching)
> - {
> - /* WinCE doesn't set an initial breakpoint automatically. To
> - stop the inferior, we flush all currently pending debug
> - events -- the thread list and the dll list are always
> - reported immediatelly without delay, then, we suspend all
> - threads and pretend we saw a trap at the current PC of the
> - main thread.
> -
> - Contrary to desktop Windows, Windows CE *does* report the dll
> - names on LOAD_DLL_DEBUG_EVENTs resulting from a
> - DebugActiveProcess call. This limits the way we can detect
> - if all the dlls have already been reported. If we get a real
> - debug event before leaving attaching, the worst that will
> - happen is the user will see a spurious breakpoint. */
> -
> - current_event.dwDebugEventCode = 0;
> - if (!wait_for_debug_event (¤t_event, 0))
> - {
> - OUTMSG2(("no attach events left\n"));
> - fake_breakpoint_event ();
> - attaching = 0;
> - }
> - else
> - OUTMSG2(("got attach event\n"));
> - }
> - else
> -#endif
> - {
> - gdb::optional<pending_stop> stop = fetch_pending_stop (debug_threads);
> - if (stop.has_value ())
> - {
> - *ourstatus = stop->status;
> - current_event = stop->event;
> - ptid = debug_event_ptid (¤t_event);
> - current_thread = find_thread_ptid (ptid);
> - return 1;
> - }
> + {
I think this brace and the matching one later on can be removed, with
a corresponding reduction in indent level for the enclosed block.
> + gdb::optional<pending_stop> stop = fetch_pending_stop (debug_threads);
> + if (stop.has_value ())
> + {
> + *ourstatus = stop->status;
> + current_event = stop->event;
> + ptid = debug_event_ptid (¤t_event);
> + current_thread = find_thread_ptid (ptid);
> + return 1;
> + }
>
> - /* Keep the wait time low enough for comfortable remote
> - interruption, but high enough so gdbserver doesn't become a
> - bottleneck. */
> - if (!wait_for_debug_event (¤t_event, 250))
> - {
> - DWORD e = GetLastError();
> + /* Keep the wait time low enough for comfortable remote
> + interruption, but high enough so gdbserver doesn't become a
> + bottleneck. */
> + if (!wait_for_debug_event (¤t_event, 250))
> + {
> + DWORD e = GetLastError();
>
> - if (e == ERROR_PIPE_NOT_CONNECTED)
> - {
> - /* This will happen if the loader fails to succesfully
> - load the application, e.g., if the main executable
> - tries to pull in a non-existing export from a
> - DLL. */
> - ourstatus->kind = TARGET_WAITKIND_EXITED;
> - ourstatus->value.integer = 1;
> - return 1;
> - }
> + if (e == ERROR_PIPE_NOT_CONNECTED)
> + {
> + /* This will happen if the loader fails to succesfully
> + load the application, e.g., if the main executable
> + tries to pull in a non-existing export from a
> + DLL. */
> + ourstatus->kind = TARGET_WAITKIND_EXITED;
> + ourstatus->value.integer = 1;
> + return 1;
> + }
>
> - return 0;
> - }
> - }
> + return 0;
> + }
> + }
I think that's the matching brace, above.
Kevin
next prev parent reply other threads:[~2020-05-14 20:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 17:43 [PATCH 0/7] Remove obsolete GDBserver ports Simon Marchi
2020-05-14 17:43 ` [PATCH 1/7] gdbserver: remove support for LynxOS Simon Marchi
2020-05-14 17:43 ` [PATCH 2/7] gdbserver: remove support for Neutrino Simon Marchi
2020-05-14 17:43 ` [PATCH 3/7] gdbserver: remove support for Blackfin Simon Marchi
2020-05-14 17:43 ` [PATCH 4/7] gdbserver: remove support for CRIS Simon Marchi
2020-05-14 17:43 ` [PATCH 5/7] gdbserver: remove support for M32R Simon Marchi
2020-05-14 17:43 ` [PATCH 6/7] gdbserver: remove support for Tile Simon Marchi
2020-05-14 18:59 ` [PATCH 0/7] Remove obsolete GDBserver ports Kevin Buettner
2020-05-14 19:12 ` Simon Marchi
2020-05-14 19:05 ` [PATCH 7/7] gdbserver: remove support for ARM/WinCE Simon Marchi
2020-05-14 20:30 ` Kevin Buettner [this message]
2020-05-14 23:14 ` Simon Marchi
2020-05-15 1:03 ` Kevin Buettner
2020-05-15 11:09 ` Pedro Alves
2020-05-14 19:07 ` [PATCH 0/7] Remove obsolete GDBserver ports Christian Biesinger
2020-05-14 19:12 ` Simon Marchi
2020-05-14 19:18 ` [PATCH 8/7] gdb: mention removed GDBserver host support in NEWS Simon Marchi
2020-05-14 19:21 ` Eli Zaretskii
2020-05-15 10:19 ` [PATCH 0/7] Remove obsolete GDBserver ports Pedro Alves
2020-05-15 14:18 ` Simon Marchi
2020-06-12 20:08 ` Simon Marchi
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=20200514133049.2297a58a@f31-4.lan \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.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