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: blarsen@redhat.com, aburgess@redhat.com
Subject: [PATCH v2 0/1] Refactor proceed function
Date: Mon, 12 Jun 2023 09:49:26 +0200	[thread overview]
Message-ID: <20230612074927.424961-1-christina.schimpe@intel.com> (raw)

Hi all,

this patch was originally written by Mihails Strasuns.  This version addresses
the feedback of Andrew to improve comments. I also added myself as co-author in
the commit message.

V1 of this patch can be found here:
https://sourceware.org/pipermail/gdb-patches/2023-June/200105.html

Regards,
Christina

Mihails Strasuns (1):
  gdb, infrun: refactor part of `proceed` into separate function

 gdb/infrun.c | 120 ++++++++++++++++++++++++++-------------------------
 1 file changed, 61 insertions(+), 59 deletions(-)

-- 
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-06-12  7:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12  7:49 Christina Schimpe [this message]
2023-06-12  7:49 ` [PATCH v2 1/1] gdb, infrun: refactor part of `proceed` into separate function Christina Schimpe
2023-06-14 10:02   ` Andrew Burgess
2023-06-16  9:50     ` Andrew Burgess
2023-06-22 14:23       ` Andrew Burgess
2023-06-28 10:14         ` 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=20230612074927.424961-1-christina.schimpe@intel.com \
    --to=christina.schimpe@intel.com \
    --cc=aburgess@redhat.com \
    --cc=blarsen@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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).