From: Yufeng Zhang <Yufeng.Zhang@arm.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Doug Evans <dje@google.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patchv3] Fix SIGTERM signal safety (PR gdb/15358)
Date: Mon, 24 Mar 2014 16:33:00 -0000 [thread overview]
Message-ID: <53305E3D.9070507@arm.com> (raw)
In-Reply-To: <20140323165745.GA23830@host2.jankratochvil.net>
Hi Jan,
On 03/23/14 16:57, Jan Kratochvil wrote:
> On Sun, 23 Mar 2014 16:19:08 +0100, Yufeng Zhang wrote:
>> On 03/16/14 13:53, Jan Kratochvil wrote:
>>> + gdb_test_no_output "set range-stepping off" ""
>>> + gdb_test_no_output "set debug infrun 1" ""
>>> + gdb_test_no_output "set debug lin-lwp 1" ""
>>
>> The test fails on aarch64-none-elf. Should the test only run on
>> Linux targets?
>
> I see that lin-lwp probably does not exist on such GDB.
>
> That "set debug lin-lwp 1" command even is not needed for the functionality of
> this testcase.
>
> Does this patch fix it on aarch64-none-elf or should it be really disabled?
The patch does fix the failure. Thanks for your help!
Thanks,
Yufeng
next prev parent reply other threads:[~2014-03-24 16:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 18:37 [patch] Fix SIGTERM signal safety (PR gdb/15358) [refresh] Jan Kratochvil
2014-03-14 18:45 ` [patchv2] " Jan Kratochvil
2014-03-15 19:44 ` Doug Evans
2014-03-16 13:53 ` [patchv3] Fix SIGTERM signal safety (PR gdb/15358) Jan Kratochvil
2014-03-17 22:35 ` Doug Evans
2014-03-18 21:51 ` [commit] " Jan Kratochvil
2014-03-23 15:19 ` Yufeng Zhang
2014-03-23 16:58 ` Jan Kratochvil
2014-03-24 16:33 ` Yufeng Zhang [this message]
2014-03-24 17:11 ` [obv commit] " Jan Kratochvil
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=53305E3D.9070507@arm.com \
--to=yufeng.zhang@arm.com \
--cc=dje@google.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