public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Christina Schimpe <christina.schimpe@intel.com>
To: gdb-patches@sourceware.org
Cc: eliz@gnu.org, blarsen@redhat.com, simark@simark.ca
Subject: [PATCH v3 0/1] Add breakpoint location debugging logs
Date: Mon, 27 Mar 2023 11:12:34 +0200	[thread overview]
Message-ID: <20230327091235.521536-1-christina.schimpe@intel.com> (raw)

Hi all,

this is my v3 for the patch "gdb, breakpoint: add breakpoint location debugging
logs", which addresses the feedback of Simon.
The documentation part has been approved by Eli.

V2 of this patch can be found here: 
https://sourceware.org/pipermail/gdb-patches/2023-March/197899.html

Changes since V2:
* Comments
* Logging output

Regards,
Christina

Mihails Strasuns (1):
  gdb, breakpoint: add breakpoint location debugging logs

 gdb/NEWS            |  4 +++
 gdb/breakpoint.c    | 73 +++++++++++++++++++++++++++++++++++++++++++++
 gdb/doc/gdb.texinfo |  8 +++++
 3 files changed, 85 insertions(+)

-- 
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-03-27  9:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27  9:12 Christina Schimpe [this message]
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

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=20230327091235.521536-1-christina.schimpe@intel.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).