From: "Puputti, Matti" <matti.puputti@intel.com>
To: "aburgess@redhat.com" <aburgess@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH v5 1/1] gdb, infcmd: Support jump command with same line in multiple symtabs
Date: Mon, 15 May 2023 08:19:30 +0000 [thread overview]
Message-ID: <SN6PR11MB3086174846F833C119C599ACED789@SN6PR11MB3086.namprd11.prod.outlook.com> (raw)
In-Reply-To: <83y1ltbonv.fsf@gnu.org>
Hi Andrew,
Thank you for the review.
Please note that the Patch 5 makes one more change in the code, by changing the error message ("Unreasonable jump request" -> "Jump request is ambiguous: does not resolve to a single address").
If you are ok with the new error message, and since Eli seems to be ok with the documentation, I think we are ready to push.
I don't yet have rights to push.
Can you please push this commit for me?
Br,
Matti Puputti
> -----Original Message-----
> From: Eli Zaretskii <eliz@gnu.org>
> Sent: Friday, May 12, 2023 4:38 PM
> To: Puputti, Matti <matti.puputti@intel.com>
> Cc: gdb-patches@sourceware.org; aburgess@redhat.com
> Subject: Re: [PATCH v5 1/1] gdb, infcmd: Support jump command with same
> line in multiple symtabs
>
> > From: Matti Puputti <matti.puputti@intel.com>
> > Cc: eliz@gnu.org,
> > aburgess@redhat.com
> > Date: Fri, 12 May 2023 15:33:20 +0200
> >
> > If a header file defining a static function is included in multiple source
> > files, each calling the function, and GDB is asked to jump to a line inside
> > that function, there would be multiple locations matching the target. The
> > solution in this commit is to select the location in the current symtab.
> > ---
> > gdb/doc/gdb.texinfo | 4 +-
> > gdb/infcmd.c | 14 ++++-
> > .../gdb.base/jump_multiple_objfiles-foo.c | 24 +++++++++
> > .../gdb.base/jump_multiple_objfiles.c | 30 +++++++++++
> > .../gdb.base/jump_multiple_objfiles.exp | 54 +++++++++++++++++++
> > .../gdb.base/jump_multiple_objfiles.h | 30 +++++++++++
> > 6 files changed, 154 insertions(+), 2 deletions(-)
> > create mode 100755 gdb/testsuite/gdb.base/jump_multiple_objfiles-foo.c
> > create mode 100755 gdb/testsuite/gdb.base/jump_multiple_objfiles.c
> > create mode 100755 gdb/testsuite/gdb.base/jump_multiple_objfiles.exp
> > create mode 100755 gdb/testsuite/gdb.base/jump_multiple_objfiles.h
>
> Thanks, the documentation part of this is OK.
>
> Reviewed-By: Eli Zaretskii <eliz@gnu.org>
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
next prev parent reply other threads:[~2023-05-15 8:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 13:33 [PATCH v5 0/1] " Matti Puputti
2023-05-12 13:33 ` [PATCH v5 1/1] " Matti Puputti
2023-05-12 14:38 ` Eli Zaretskii
2023-05-15 8:19 ` Puputti, Matti [this message]
2023-05-22 8:01 ` [PING][PATCH " Puputti, Matti
2023-05-24 12:51 ` Andrew Burgess
2023-05-24 16:03 ` Andrew Burgess
2023-05-25 5:38 ` 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=SN6PR11MB3086174846F833C119C599ACED789@SN6PR11MB3086.namprd11.prod.outlook.com \
--to=matti.puputti@intel.com \
--cc=aburgess@redhat.com \
--cc=eliz@gnu.org \
--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).