public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Bruno Larsen <blarsen@redhat.com>
To: "Puputti, Matti" <matti.puputti@intel.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2 1/1] gdb, infcmd: Support jump command with same line in multiple symtabs
Date: Mon, 17 Apr 2023 15:40:59 +0200	[thread overview]
Message-ID: <6c66d257-b1f3-6dfa-7a75-bc74a22af26c@redhat.com> (raw)
In-Reply-To: <SN6PR11MB30864B414F92EA7E7E865BC9ED9C9@SN6PR11MB3086.namprd11.prod.outlook.com>

On 17/04/2023 13:33, Puputti, Matti wrote:
> Hi Bruno,
>
> I have just now uploaded third patch, with updated commit message.
> https://sourceware.org/pipermail/gdb-patches/2023-April/198912.html
>
> If you are good with the new patch, may I ask a favour: can you please push it for me?  I don't have write access, as this this is my first patch series (potentially) to be approved.

Hi Matti,

I don't have the authority to actually approve patches for merging, I 
just review them as a way to signal to the maintainers who can actually 
approve that it has passed my review and so (hopefully) doesn't contain 
obvious mistakes, making their lives easier. The tag you'd be looking 
for is Approved-by. Sorry if this was confusing

-- 
Cheers,
Bruno

>
> Br,
> Matti Puputti
>
>> -----Original Message-----
>> From: Bruno Larsen <blarsen@redhat.com>
>> Sent: Monday, April 17, 2023 12:17 PM
>> To: Puputti, Matti <matti.puputti@intel.com>; gdb-patches@sourceware.org
>> Subject: Re: [PATCH v2 1/1] gdb, infcmd: Support jump command with same line
>> in multiple symtabs
>>
>> Hi Matti,
>>
>> Only some small nits on the commit message:
>>
>> On 14/04/2023 16:15, Matti Puputti wrote:
>>> For example, a header file defining a static function is included in multiple
>> Starting with "If a header (...)" makes more sense in my opinion
>>> source files, each calling the function.  When debugger is asked to jump to
>> "When the debugger" or "When GDB" would flow better
>>> a line inside that function, there would be multiple locations matching the
>>> target.  Solution in this commit is to select the location in the current
>> "The solution in this commit", as mentioend above
>>> symtab.
>> With these changes, I'm fine with giving you my tag:
>> Reviewed-By: Bruno Larsen <blarsen@redhat.com>
>>
>> --
>> Cheers,
>> Bruno
>>
> 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-04-17 13:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-14 14:15 [PATCH v2 0/1] " Matti Puputti
2023-04-14 14:15 ` [PATCH v2 1/1] " Matti Puputti
2023-04-17 10:16   ` Bruno Larsen
2023-04-17 11:33     ` Puputti, Matti
2023-04-17 13:40       ` Bruno Larsen [this message]
2023-04-17 15:21         ` Puputti, Matti

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=6c66d257-b1f3-6dfa-7a75-bc74a22af26c@redhat.com \
    --to=blarsen@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=matti.puputti@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).