This is the mail archive of the
gdb-testers@sourceware.org
mailing list for the GDB project.
Re: diffgdbdaymail 20141029
- From: Pedro Alves <palves at redhat dot com>
- To: diffgdbdaymail by Jan Kratochvil <jan dot kratochvil at redhat dot com>, gdb-testers at sourceware dot org
- Date: Wed, 29 Oct 2014 16:20:18 +0000
- Subject: Re: diffgdbdaymail 20141029
- Authentication-results: sourceware.org; auth=none
- References: <201410291149 dot s9TBnFmS031277 at host1 dot jankratochvil dot net>
On 10/29/2014 11:49 AM, diffgdbdaymail by Jan Kratochvil wrote:
> --- 20141028Build-gdbgit-f20/fedora-20-x86_64/out/gdb-m32.sum 2014-10-28 10:12:27.757881095 +0100
> --- GIT commit 6fb9c0f83252a79b2f1a3f8e75fa117ca7a4d589
> +++ 20141029Build-gdbgit-f20/fedora-20-x86_64/out/gdb-m32.sum 2014-10-29 09:52:20.310537452 +0100
> +++ GIT commit 6ae274b7dc305ae7cebcf55c5018dab05228235a
>
> #gdb.arch/i386-bp_permanent.exp
> Running gdb/testsuite/gdb.arch/i386-bp_permanent.exp ...
> PASS: gdb.arch/i386-bp_permanent.exp: Stop at the 'standard' start breakpoint (fetching esp).
> PASS: gdb.arch/i386-bp_permanent.exp: Stop at permanent breakpoint.
> -PASS: gdb.arch/i386-bp_permanent.exp: Single stepping past permanent breakpoint.
> -PASS: gdb.arch/i386-bp_permanent.exp: ESP value does not match - step_permanent_breakpoint wrong.
> +FAIL: gdb.arch/i386-bp_permanent.exp: Single stepping past permanent breakpoint. (GDB internal error)
> +FAIL: gdb.arch/i386-bp_permanent.exp: ESP value does not match - step_permanent_breakpoint wrong.
Mine. The test is skipped on 64-bit, and seems like I missed the case
of stepping permanent breakpoints.
(gdb) PASS: gdb.arch/i386-bp_permanent.exp: Stop at permanent breakpoint.
stepi
../../src/gdb/infrun.c:2237: internal-error: resume: Assertion `sig != GDB_SIGNAL_0' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) FAIL: gdb.arch/i386-bp_permanent.exp: Single stepping past permanent breakpoint. (GDB internal error)
Resyncing due to internal error.
n
This is a bug, please report it. For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.
../../src/gdb/infrun.c:2237: internal-error: resume: Assertion `sig != GDB_SIGNAL_0' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) n
0x080484ad in standard ()
Command aborted.
(gdb) print $esp
$2 = (void *) 0xffffc334
(gdb) FAIL: gdb.arch/i386-bp_permanent.exp: ESP value does not match - step_permanent_breakpoint wrong.
> --- 20141028Build-gdbgit-f20/fedora-20-i386/out/gdb-m32.sum 2014-10-28 10:06:01.246896711 +0100
> --- GIT commit 6fb9c0f83252a79b2f1a3f8e75fa117ca7a4d589
> +++ 20141029Build-gdbgit-f20/fedora-20-i386/out/gdb-m32.sum 2014-10-29 09:45:30.596547803 +0100
> +++ GIT commit 6ae274b7dc305ae7cebcf55c5018dab05228235a
>
> #gdb.arch/i386-bp_permanent.exp
> Running gdb/testsuite/gdb.arch/i386-bp_permanent.exp ...
> PASS: gdb.arch/i386-bp_permanent.exp: Stop at the 'standard' start breakpoint (fetching esp).
> PASS: gdb.arch/i386-bp_permanent.exp: Stop at permanent breakpoint.
> -PASS: gdb.arch/i386-bp_permanent.exp: Single stepping past permanent breakpoint.
> -PASS: gdb.arch/i386-bp_permanent.exp: ESP value does not match - step_permanent_breakpoint wrong.
> +FAIL: gdb.arch/i386-bp_permanent.exp: Single stepping past permanent breakpoint. (GDB internal error)
> +FAIL: gdb.arch/i386-bp_permanent.exp: ESP value does not match - step_permanent_breakpoint wrong.
> +FAIL: gdb.base/sigstep.exp: stepi to handler, si+advance in handler, step from handler: advance in handler (spurious SIGTRAP)
Mine as well. 32-bit needs to be kfailed too.
Thanks,
Pedro Alves