This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v2 01/13] gdb/linux-record: Add testcases for a few syscalls.
- From: Pedro Alves <palves at redhat dot com>
- To: Marcin KoÅcielnicki <koriakin at 0x04 dot net>, qiyaoltc at gmail dot com
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 30 Oct 2015 10:37:31 +0000
- Subject: Re: [PATCH v2 01/13] gdb/linux-record: Add testcases for a few syscalls.
- Authentication-results: sourceware.org; auth=none
- References: <5628E5D6 dot 5020706 at 0x04 dot net> <1445521166-14492-1-git-send-email-koriakin at 0x04 dot net> <5632035E dot 30809 at redhat dot com> <56327421 dot 6090203 at 0x04 dot net>
On 10/29/2015 07:31 PM, Marcin KoÅcielnicki wrote:
>>> +
>>> +gdb_test "break marker1" \
>>> + "Breakpoint $decimal at $hex: file .*$srcfile, line $decimal.*" \
>>> + "set breakpoint at marker1"
>>> +
>>> +gdb_test "break marker2" \
>>> + "Breakpoint $decimal at $hex: file .*$srcfile, line $decimal.*" \
>>> + "set breakpoint at marker2"
>>> +
>>> +gdb_continue_to_breakpoint "marker1" ".*$srcfile:.*"
>>> +
>>> +gdb_continue_to_breakpoint "marker2" ".*$srcfile:.*"
>>
>> Most (all?) these tests run to marker1 and then immediately to
>> marker2. Can't they just continue to marker2 directly?
>>
>
> Huh. I've done that and, funnily enough, the waitpid testcase magically
> started to pass.
Eh.
> For the record, I've reported the bug here:
> https://sourceware.org/bugzilla/show_bug.cgi?id=19187
Thanks.
> I guess there won't be a KFAIL after all.
>
OK.
I'll take a look at the new version.
Thanks,
Pedro Alves