[Bug testsuite/26915] New: FAIL: gdb.threads/schedlock.exp: schedlock=off: cmd=next: call_function=0: other threads ran - unlocked

[Bug testsuite/26915] New: FAIL: gdb.threads/schedlock.exp: schedlock=off: cmd=next: call_function=0: other threads ran - unlocked

[vries at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=26915

            Bug ID: 26915
           Summary: FAIL: gdb.threads/schedlock.exp: schedlock=off:
                    cmd=next: call_function=0: other threads ran -
                    unlocked
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

In more detail:
...
(gdb) PASS: gdb.threads/schedlock.exp: schedlock=off: cmd=next:
call_function=0: find current thread (after)
PASS: gdb.threads/schedlock.exp: schedlock=off: cmd=next: call_function=0: next
does not change thread
print args^M
$9 = {135109772, 453620604}^M
(gdb) PASS: gdb.threads/schedlock.exp: schedlock=off: cmd=next:
call_function=0: listed args (after)
PASS: gdb.threads/schedlock.exp: schedlock=off: cmd=next: call_function=0:
current thread advanced - unlocked
FAIL: gdb.threads/schedlock.exp: schedlock=off: cmd=next: call_function=0:
other threads ran - unlocked
...

This is with a local obs build with vm-type=kvm, so AFAIU, the setup is that
the leap 15.2 kernel provides the kvm to run the tumbleweed kernel.

ISTM that while having schedlock=off allows other threads to run, it doesn't
guarantee they do, so I'm not sure there's a gdb problem here.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug testsuite/26915] FAIL: gdb.threads/schedlock.exp: schedlock=off: cmd=next: call_function=0: other threads ran - unlocked

[vries at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=26915

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 12974
  --> https://sourceware.org/bugzilla/attachment.cgi?id=12974&action=edit
gdb.log

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug testsuite/26915] FAIL: gdb.threads/schedlock.exp: schedlock=off: cmd=next: call_function=0: other threads ran - unlocked

[vries at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=26915

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
FWIW, the fedora test-case gdb.threads/watchthreads-threaded.exp from
gdb-6.3-threaded-watchpoints2-20050225.patch seems to suffer from the same
problem (and claims to be copied from schedlock.c):
...
FAIL: gdb.threads/watchthreads-threaded.exp: watchpoint on args[3] hit in
thread
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.