This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [pushed] Add test for PR18214 and PR18216 - multiple step-overs with queued signals
- From: Yao Qi <qiyaoltc at gmail dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 09 Apr 2015 17:46:05 +0100
- Subject: Re: [pushed] Add test for PR18214 and PR18216 - multiple step-overs with queued signals
- Authentication-results: sourceware.org; auth=none
- References: <1428519576-12754-1-git-send-email-palves at redhat dot com>
Pedro Alves <palves@redhat.com> writes:
> For good measure, I made the test try displaced stepping too. And
> then I found it crashes GDB on x86-64 (a hardware step target), but
> only when displaced stepping... :
Turning displaced stepping on also exposes some problems on arm-linux
too, besides these two kfails, there are also:
FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: step
FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: next
FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: continue
FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: continue to sigusr1_handler
step^M
[Switching to Thread 30857]^M
^M
Breakpoint 4, child_function_2 (arg=0x0) at /home/yao/SourceCode/gnu/gdb/git/gdb/testsuite/gdb.threads/multiple-step-overs.c:66^M
66 callme (); /* set breakpoint thread 2 here */^M
(gdb) FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: step
next^M
[Switching to Thread 30941]^M
^M
Breakpoint 4, child_function_2 (arg=0x0) at /home/yao/SourceCode/gnu/gdb/git/gdb/testsuite/gdb.threads/multiple-step-overs.c:66^M
66 callme (); /* set breakpoint thread 2 here */^M
(gdb) FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: next
I'll analyse them tomorrow.
--
Yao (éå)