public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Puputti, Matti" <matti.puputti@intel.com>
To: Andrew Burgess <aburgess@redhat.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH v6 1/1] gdb, infcmd: Support jump command in multi-inferior case.
Date: Wed, 16 Aug 2023 10:55:05 +0000	[thread overview]
Message-ID: <SN6PR11MB30869CC050F397C2C05BFC9DED15A@SN6PR11MB3086.namprd11.prod.outlook.com> (raw)
In-Reply-To: <87bkf7cqif.fsf@redhat.com>

Hi Andrew,

Thank you for the support.

Br,
Matti Puputti

> -----Original Message-----
> From: Andrew Burgess <aburgess@redhat.com>
> Sent: Wednesday, August 16, 2023 10:59 AM
> To: Puputti, Matti <matti.puputti@intel.com>; gdb-patches@sourceware.org
> Subject: Re: [PATCH v6 1/1] gdb, infcmd: Support jump command in multi-
> inferior case.
> 
> Matti Puputti <matti.puputti@intel.com> writes:
> 
> > From: "Puputti, Matti" <matti.puputti@intel.com>
> >
> > Fixes the issue where jump failed if multiple inferiors run the same
> > source.
> 
> Thanks for the latest update.
> 
> I took another look through, this looks great, so I have pushed this to
> master.
> 
> I did add a new comment to the 'do_test' proc in the test script, and
> extended the description of the fix in the commit message.
> 
> Thanks,
> Andrew
> 
> 
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-08-16 10:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26 12:29 Matti Puputti
2023-08-16  8:58 ` Andrew Burgess
2023-08-16 10:55   ` Puputti, Matti [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=SN6PR11MB30869CC050F397C2C05BFC9DED15A@SN6PR11MB3086.namprd11.prod.outlook.com \
    --to=matti.puputti@intel.com \
    --cc=aburgess@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).