From: Simon Marchi <simon.marchi@ericsson.com>
To: Phil Muldoon <pmuldoon@redhat.com>,
Simon Marchi <simon.marchi@polymtl.ca>
Cc: Keith Seitz <keiths@redhat.com>, <palves@redhat.com>,
<eliz@gnu.org>, <gdb-patches@sourceware.org>
Subject: Re: [python] Allow explicit locations in breakpoints.
Date: Thu, 07 Dec 2017 16:41:00 -0000 [thread overview]
Message-ID: <81dd7186-a76b-0412-5689-57082a5f5aad@ericsson.com> (raw)
In-Reply-To: <22a365d9-48b6-2330-5bbe-13115d0404a7@redhat.com>
On 2017-12-07 10:12 AM, Phil Muldoon wrote:
> Apologies, my github branch was more behind master than I at first
> thought. I've attached the update patch.
>
> Cheers,
>
> Phil
>
Hi Phil,
That version is fine with me. As mentioned on IRC, it would be nice to
have a Python parameter equivalent to the -q/--qualified CLI switch. I'd
be fine with it being done as another patch on top.
Simon
next prev parent reply other threads:[~2017-12-07 16:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <04ccc2c4-7827-eedc-d8db-a83a0167acb6@redhat.com>
2017-08-23 17:51 ` Keith Seitz
2017-08-23 18:31 ` Phil Muldoon
2017-10-16 18:23 ` Simon Marchi
2017-10-16 18:33 ` Simon Marchi
2017-10-16 20:24 ` Phil Muldoon
2017-10-16 21:26 ` Simon Marchi
2017-10-16 22:01 ` Phil Muldoon
2017-10-16 22:26 ` Simon Marchi
2017-11-17 11:02 ` Phil Muldoon
2017-11-17 13:31 ` Eli Zaretskii
2017-11-17 14:02 ` Phil Muldoon
2017-11-23 22:17 ` Simon Marchi
2017-11-24 14:07 ` Phil Muldoon
2017-12-07 10:02 ` Phil Muldoon
2017-12-07 12:16 ` Phil Muldoon
2017-12-07 14:54 ` Simon Marchi
2017-12-07 15:12 ` Phil Muldoon
2017-12-07 16:41 ` Simon Marchi [this message]
2017-12-08 13:50 ` Eli Zaretskii
2017-09-12 10:03 ` Phil Muldoon
2017-10-02 15:18 ` Phil Muldoon
2017-10-16 11:14 ` Phil Muldoon
2017-10-16 18:31 ` Simon Marchi
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=81dd7186-a76b-0412-5689-57082a5f5aad@ericsson.com \
--to=simon.marchi@ericsson.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
--cc=palves@redhat.com \
--cc=pmuldoon@redhat.com \
--cc=simon.marchi@polymtl.ca \
/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