From: Carl Love <cel@linux.ibm.com>
To: Luis Machado <luis.machado@arm.com>,
gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Cc: Guinevere Larsen <blarsen@redhat.com>,
Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Subject: Re: [PATCH ver 2] Fix the gdb.ada/inline-section-gc.exp test
Date: Wed, 08 Nov 2023 10:02:37 -0800 [thread overview]
Message-ID: <290c84968ebe8a82359e28cf49b50dc79a21845c.camel@linux.ibm.com> (raw)
In-Reply-To: <54a336be-249d-40e9-b4e0-68602734ce26@arm.com>
Luis, Tom:
On Wed, 2023-11-08 at 16:57 +0000, Luis Machado wrote:
> Hi Carl,
>
> This fixes the FAIL's I had been seeing on aarch64-linux. Thanks!
>
> Some nits...
>
>
<snip>
> > file callee.adb or in
> > +# file caller.adb where the callee function was inlined. Either
> > way, only
> > +# on breakpoint should be reported and it's address should not be
> > at 0x0.
> s/on breakpoint/one breakpoint?
>
> s/and it's/and its?
Fixed both issues.
On Wed, 2023-11-08 at 09:54 -0700, Tom Tromey wrote:> > > > > > "Carl"
<snip>
>
> I think it looks good, but I have one nit.
>
> Carl> +set bp_location1 [gdb_get_line_number "BREAK"
> ${testdir}/callee.adb]
> Carl> +set bp_location2 [expr $bp_location1 - 1]
>
> It would be better to just stick some comment on the relevant line in
> caller.adb and then use gdb_get_line_number to fetch it.
OK, that works. I added a comment to set the line number on. The
comment has to be placed on the line in caller where the BREAK line
ends up after callee is inlined into caller, which is not really
obvious at first glance. I worked hard to make it clear in the comment
and the commit log. Hopefully it is clear to the reader.
Will post version 3.
Thanks for the feedback and help with the patch.
Carl
prev parent reply other threads:[~2023-11-08 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 16:22 Carl Love
2023-11-08 16:54 ` Tom Tromey
2023-11-08 16:57 ` Luis Machado
2023-11-08 18:02 ` Carl Love [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=290c84968ebe8a82359e28cf49b50dc79a21845c.camel@linux.ibm.com \
--to=cel@linux.ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.com \
--cc=tom@tromey.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