1. 24 Jun, 2011 2 commits
  2. 22 Jun, 2011 1 commit
  3. 17 Jun, 2011 3 commits
  4. 15 Jun, 2011 4 commits
  5. 14 Jun, 2011 2 commits
  6. 13 Jun, 2011 2 commits
  7. 10 Jun, 2011 1 commit
  8. 08 Jun, 2011 6 commits
  9. 06 Jun, 2011 1 commit
  10. 03 Jun, 2011 1 commit
    • Daniel Drake's avatar
      Fix GC-related crash during PyGObject deallocation · 92aca441
      Daniel Drake authored
      Python-2.7.1's GC source has the following comment:
      
              /* Python's cyclic gc should never see an incoming refcount
               * of 0:  if something decref'ed to 0, it should have been
               * deallocated immediately at that time.
               * Possible cause (if the assert triggers):  a tp_dealloc
               * routine left a gc-aware object tracked during its teardown
               * phase, and did something-- or allowed something to happen --
               * that called back into Python.  gc can trigger then, and may
               * see the still-tracked dying object.  Before this assert
               * was added, such mistakes went on to allow gc to try to
               * delete the object again.  In a debug build, that caused
               * a mysterious segfault, when _Py_ForgetReference tried
               * to remove the object from the doubly-linked list of all
               * objects a second time.  In a release build, an actual
               * double deallocation occurred, which leads to corruption
               * of the allocator's internal bookkeeping pointers.  That's
               * so serious that maybe this should be a release-build
               * check instead of an assert?
               */
      
      As shown in a backtrace at
      https://bugzilla.redhat.com/show_bug.cgi?id=640972 , pygobject is making
      this exact mistake. Before untracking its object, pygobject_dealloc
      calls PyObject_ClearWeakRefs() which can call back into python, create
      new allocations, and trigger the GC.
      
      This is causing Sugar (based on pygobject2 + pygtk2 static bindings) to
      crash on a regular basis while interacting with widgets or launching
      applications.
      
      Fix this by untracking the object early. Also fix the same issue spotted
      in the GSource wrapper.
      
      Thanks to Bernie Innocenti for initial diagnosis.
      92aca441
  11. 31 May, 2011 5 commits
  12. 26 May, 2011 4 commits
  13. 23 May, 2011 2 commits
  14. 12 May, 2011 2 commits
  15. 09 May, 2011 1 commit
    • Jos茅 Alburquerque's avatar
      Doc Extractor: Add a --no-since option. · 303d8e8a
      Jos茅 Alburquerque authored
      	* codegen/docextract.py:
      	* codegen/docextract_to_xml.py: Modified so that if a --no-since
      	option is specified at the command line, the "Since: ..." portion of
      	the gtkdoc function block is omitted.  This is useful for C++ modules
      	such as gstreamermm where this information would not be useful as long
      	as the C API is still unstable.
      303d8e8a
  16. 05 May, 2011 1 commit
  17. 04 May, 2011 2 commits