From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Regression with default scheduler-locking=step [Re: [pushed] Consecutive step-overs trigger internal error.]
Date: Thu, 19 Jun 2014 11:30:00 -0000 [thread overview]
Message-ID: <53A2C9CA.4060802@redhat.com> (raw)
In-Reply-To: <20140618175709.GA9237@host2.jankratochvil.net>
On 06/18/2014 06:57 PM, Jan Kratochvil wrote:
> On Wed, 18 Jun 2014 15:52:13 +0200, Pedro Alves wrote:
>> Here's a fix. Let me know what you think.
>
> The change looks OK and as it fixes the assertion I am for the patch.
Thanks. Now pushed to both master and gdb-7.8-branch.
--
Pedro Alves
prev parent reply other threads:[~2014-06-19 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 18:24 [pushed] Consecutive step-overs trigger internal error Pedro Alves
2014-06-17 19:24 ` Regression with default scheduler-locking=step [Re: [pushed] Consecutive step-overs trigger internal error.] Jan Kratochvil
2014-06-18 13:52 ` Pedro Alves
2014-06-18 17:57 ` Jan Kratochvil
2014-06-19 11:30 ` 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=53A2C9CA.4060802@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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).