This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug breakpoints/17175] New: FAIL: gdb.threads/multiple-step-overs.exp: next
- From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 18 Jul 2014 11:19:11 +0000
- Subject: [Bug breakpoints/17175] New: FAIL: gdb.threads/multiple-step-overs.exp: next
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=17175
Bug ID: 17175
Summary: FAIL: gdb.threads/multiple-step-overs.exp: next
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: breakpoints
Assignee: unassigned at sourceware dot org
Reporter: jan.kratochvil at redhat dot com
Depends on: 17174
Host: x86_64-linux-gnu
Target: x86_64-linux-gnu
Only on CentOS-5 and CentOS-6 (IMO OSes without longjmp probes) for 32-bit
targets (x86_64-m32 and i686; not for x86_64) I get
infrun: BPSTAT_WHAT_SET_LONGJMP_RESUME^M
infrun: inserting longjmp-resume breakpoint at 0x8c0d289e^M
Warning:^M
Cannot insert breakpoint 0.^M
Cannot access memory at address 0x8c0d289e^M
^M
infrun: stop_stepping^M
[Switching to Thread 0xf75f1b70 (LWP 24297)]^M
__libc_siglongjmp (env=0xf75f1454, val=1) at longjmp.c:30^M
30 {^M
(gdb) FAIL: gdb.threads/multiple-step-overs.exp: next
At about 1st to 6th run.
It happens already on the first check-in of this testcase:
99619beac6252113fed212fdb9e1ab97bface423
It still happens on current FSF GDB trunk:
fe1873d01904620c71a309249c0ae029e53ae0b6
See also: PR 17174
--
You are receiving this mail because:
You are on the CC list for the bug.