From: Simon Marchi <simark@simark.ca>
To: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/3] gdb/breakpoint: set the condition exp after parsing the condition successfully
Date: Thu, 30 Jul 2020 11:15:28 -0400 [thread overview]
Message-ID: <85805cfb-c611-cb70-557e-62d25710abe9@simark.ca> (raw)
In-Reply-To: <SN6PR11MB28934729BFA7FA93776EEDA9C4710@SN6PR11MB2893.namprd11.prod.outlook.com>
On 2020-07-30 6:56 a.m., Aktemur, Tankut Baris wrote:
> On Thursday, July 23, 2020 9:11 AM, Aktemur, Tankut Baris wrote:
>> On Wednesday, July 22, 2020 6:06 PM, Simon Marchi wrote:
>>> Ok, so do you want to wait and post everything together, or do still want to consider
>>> merging this one on its own, since it's still a step forward?
>>
>> I'd like to merge this on its own.
>
> Hi Simon,
>
> OK to push the two-pass version?
>
> Thanks
> -Baris
Yes, go ahead.
Simon
next prev parent reply other threads:[~2020-07-30 15:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 13:48 [PATCH 0/3] Prevent bad conditions from putting breakpoints into broken state Tankut Baris Aktemur
2020-06-29 13:48 ` [PATCH 1/3] gdb/breakpoint: do not update the condition string if parsing the condition fails Tankut Baris Aktemur
2020-07-22 13:12 ` Simon Marchi
2020-07-22 13:15 ` Simon Marchi
2020-06-29 13:48 ` [PATCH 2/3] gdb/breakpoint: set the condition exp after parsing the condition successfully Tankut Baris Aktemur
2020-07-22 13:21 ` Simon Marchi
2020-07-22 13:28 ` Simon Marchi
2020-07-22 15:29 ` Aktemur, Tankut Baris
2020-07-22 16:06 ` Simon Marchi
2020-07-23 7:11 ` Aktemur, Tankut Baris
2020-07-30 10:56 ` Aktemur, Tankut Baris
2020-07-30 15:15 ` Simon Marchi [this message]
2020-06-29 13:48 ` [PATCH 3/3] gdb/breakpoint: refactor 'set_breakpoint_condition' Tankut Baris Aktemur
2020-07-13 8:45 ` [PATCH 0/3] Prevent bad conditions from putting breakpoints into broken state Tankut Baris Aktemur
2020-07-21 9:08 ` Tankut Baris Aktemur
2020-07-22 18:24 ` Pedro Alves
2020-07-23 7:13 ` Aktemur, Tankut Baris
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=85805cfb-c611-cb70-557e-62d25710abe9@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=tankut.baris.aktemur@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).