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 python/23615] New: release the GIL in execute_command


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

            Bug ID: 23615
           Summary: release the GIL in execute_command
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: python
          Assignee: unassigned at sourceware dot org
          Reporter: tromey at sourceware dot org
  Target Milestone: ---

This comes from
https://stackoverflow.com/questions/52098116/gdb-execute-blocks-all-the-threads-in-python-scripts

gdb.execute_command is called with the GIL and does not release it.
This means that other Python threads will be blocked by the gdb operation.

It would be better to release the GIL when re-entering gdb and
then re-acquire it when re-entering Python.

This should probably apply to parse_and_eval as well.

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