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 gdb/16767] New: allow non-stop to be turned on/off in debugging session


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

            Bug ID: 16767
           Summary: allow non-stop to be turned on/off in debugging
                    session
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: xdje42 at gmail dot com

IWBN if non-stop could be turned on/off while debugging an inferior.
Obviously, the transitions need to be appropriately handled.
As a first cut, I would be ok with flagging an error if all threads weren't
currently stopped.  Once "interrupt -a" is fixed (working on it ...), the error
message could suggest the user do that.
[I myself am not comfortable with "set non-stop off" when there are threads
running to actually cause those threads to be stopped.  But if they are all
stopped, is there a deep reason to not allow non-stop be changed?]

-- 
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]