From: "Schimpe, Christina" <christina.schimpe@intel.com>
To: Simon Marchi <simark@simark.ca>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "eliz@gnu.org" <eliz@gnu.org>, "blarsen@redhat.com" <blarsen@redhat.com>
Subject: RE: [PATCH v3 1/1] gdb, breakpoint: add breakpoint location debugging logs
Date: Thu, 1 Jun 2023 13:11:44 +0000 [thread overview]
Message-ID: <CY4PR11MB2005FFB972392C74F6D38972F9499@CY4PR11MB2005.namprd11.prod.outlook.com> (raw)
In-Reply-To: <a3cd9915-afa6-f073-7f42-f270d6ba0a41@simark.ca>
Hi Simon,
Thanks a lot for your review.
> Another little nit: for consistency, let's add a remove_bp_reason_str function to
> convert an enum remove_bp_reason to a string (same as you did for
> ugll_insert_mode). This way we'll get an assertion failure if we add a new
> enumerator and for got to handle it in the switch.
>
> And for all functions of this kind, I would be tempted to use
> DIAGNOSTIC_ERROR_SWITCH, like we have in the target_waitkind_str), so that
> compilers that support it can warn if we miss an enumerator in the switch.
Your comments make sense to me, I will post a v4 soon.
Christina
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
prev parent reply other threads:[~2023-06-01 13:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 9:12 [PATCH v3 0/1] Add " Christina Schimpe
2023-03-27 9:12 ` [PATCH v3 1/1] gdb, breakpoint: add " Christina Schimpe
2023-03-27 14:10 ` Andrew Burgess
2023-06-01 13:05 ` Schimpe, Christina
2023-03-27 14:47 ` Simon Marchi
2023-06-01 13:11 ` Schimpe, Christina [this message]
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=CY4PR11MB2005FFB972392C74F6D38972F9499@CY4PR11MB2005.namprd11.prod.outlook.com \
--to=christina.schimpe@intel.com \
--cc=blarsen@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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).