From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Do not respawn signals, take 2.
Date: Thu, 28 Jun 2012 17:32:00 -0000 [thread overview]
Message-ID: <20120628173135.GA23347@host2.jankratochvil.net> (raw)
In-Reply-To: <4FEC9405.7030503@redhat.com>
On Thu, 28 Jun 2012 19:27:33 +0200, Pedro Alves wrote:
> I found a couple ARM machines. This revision of the patch showed no regressions on
> {x86_64,ARM} {native,gdbserver} GNU/Linux, and the new tests fully pass. I've
> also done the promised re-indent in infrun.c.
Thanks, I was stepping around the ARM issue with this patch for the last year.
Jan
prev parent reply other threads:[~2012-06-28 17:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 14:55 Pedro Alves
2012-06-22 15:05 ` Jan Kratochvil
2012-06-22 15:12 ` Pedro Alves
2012-06-22 16:07 ` Jan Kratochvil
2012-06-28 17:51 ` x86 incomplete/WIP software single-step implementation (Re: [PATCH] Do not respawn signals, take 2.) Pedro Alves
2012-07-04 15:35 ` Pedro Alves
2012-07-04 19:45 ` Mark Kettenis
2012-06-22 19:18 ` [PATCH] Do not respawn signals, take 2 Jan Kratochvil
2012-06-28 17:28 ` Pedro Alves
2012-06-28 17:32 ` Jan Kratochvil [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=20120628173135.GA23347@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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