From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] "break LINENO/*ADDRESS", inline functions and "info break" output
Date: Fri, 29 Jun 2018 18:43:00 -0000 [thread overview]
Message-ID: <56677f78-3a52-33b6-83f0-5a83766c9bb0@redhat.com> (raw)
In-Reply-To: <20180628174203.GC2511@adacore.com>
On 06/28/2018 06:42 PM, Joel Brobecker wrote:
>> gdb/testsuite/ChangeLog:
>> yyyy-mm-dd Pedro Alves <palves@redhat.com>
>>
>> * gdb.opt/inline-break.exp (line number, address): Add "info
>> break" tests.
>
> I went through the patch and it looks good.
Great, thanks. I pushed in both patches now.
Thanks,
Pedro Alves
prev parent reply other threads:[~2018-06-29 18:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 15:06 [PATCH] Ensure captured_main has unique address Tom de Vries
2018-06-12 17:38 ` Change inline frame breakpoint skipping logic (Re: [PATCH] Ensure captured_main has unique address) Pedro Alves
2018-06-14 13:22 ` Tom de Vries
[not found] ` <8c7ace90-f0b8-56f0-0033-5b7827796037@redhat.com>
2018-06-25 21:04 ` [pushed] Change inline frame breakpoint skipping logic (fix gdb.gdb/selftest.exp) Joel Brobecker
2018-06-26 19:02 ` Pedro Alves
2018-06-26 22:02 ` Joel Brobecker
2018-06-27 16:28 ` Pedro Alves
2018-06-28 14:48 ` Pedro Alves
2018-06-28 14:50 ` [PATCH 1/2] Fix running to breakpoint set in inline function by lineno/address Pedro Alves
2018-06-28 17:32 ` Joel Brobecker
2018-06-28 14:50 ` [PATCH 2/2] "break LINENO/*ADDRESS", inline functions and "info break" output Pedro Alves
2018-06-28 17:42 ` Joel Brobecker
2018-06-29 18:43 ` Pedro Alves [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=56677f78-3a52-33b6-83f0-5a83766c9bb0@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.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