This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug threads/14618] New: scheduler-locking doesn't work withgdbserver


http://sourceware.org/bugzilla/show_bug.cgi?id=14618

             Bug #: 14618
           Summary: scheduler-locking doesn't work with gdbserver
           Product: gdb
           Version: 7.4
            Status: NEW
          Severity: critical
          Priority: P2
         Component: threads
        AssignedTo: unassigned@sourceware.org
        ReportedBy: tom.tan@analog.com
    Classification: Unclassified


I got this when running the gdb test case "gdb.threads/no-unwaited-for-left"
with remote target(gdbserver).

Everytime if I "set scheduler-locking on" in gdb and then resume from a thread,
the other threads will also be resumed. I think the "on" mode should only
resume the current thread.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]