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/13374] New: bad GIL uses


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

             Bug #: 13374
           Summary: bad GIL uses
           Product: gdb
           Version: unknown
            Status: NEW
          Severity: normal
          Priority: P2
         Component: python
        AssignedTo: unassigned@sourceware.org
        ReportedBy: tromey@redhat.com
    Classification: Unclassified


While reading the code I found a couple of spots where
the GIL is treated weirdly.

I don't see why gdbpy_decode_line should acquire the GIL.
This function will only be called in a Python context.

Acquiring the GIL in inferior_to_inferior object seems weird.
It isn't necessarily incorrect but it seems like it would be
preferable to acquire this in whichever callers need it;
usually these X_to_X_object calls are expected to be used in
a Python context.

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