1. 24 Apr, 2010 1 commit
  2. 23 Apr, 2010 1 commit
  3. 19 Apr, 2010 4 commits
    • Matthias Clasen's avatar
      Bump version · 4c276d05
      Matthias Clasen authored
      4c276d05
    • Matthias Clasen's avatar
      Bump version · ca4f0a3d
      Matthias Clasen authored
      ca4f0a3d
    • Matthias Clasen's avatar
      Reset interface age to 0 · 80ac5df9
      Matthias Clasen authored
      80ac5df9
    • Tor Lillqvist's avatar
      Add GWin32InputStream and GWin32OutputStream classes · 9af8b832
      Tor Lillqvist authored
      Correspond to GUnixInputStream and GUnixOutputStream. No true async
      support though. But that is how the Win32 API is, for files not
      explicitly opened for so-called overlapped IO.
      
      The API to create these streams takes Win32 HANDLEs. Not file
      descriptors, because file descriptors are specific to the C library
      used. The user code and GLib might be using different C libraries.
      
      Also add a test program for the new classes, and a gio-windows-2.0.pc
      file.
      9af8b832
  4. 16 Apr, 2010 1 commit
  5. 26 Mar, 2010 2 commits
  6. 22 Mar, 2010 1 commit
  7. 21 Mar, 2010 1 commit
  8. 08 Mar, 2010 1 commit
  9. 22 Feb, 2010 1 commit
  10. 21 Feb, 2010 1 commit
  11. 15 Feb, 2010 1 commit
  12. 09 Feb, 2010 1 commit
  13. 03 Feb, 2010 1 commit
  14. 28 Jan, 2010 2 commits
    • Allison Karlitskaya's avatar
      Bug 548967 - 1 bit mutex lock: add tests · 40eae351
      Allison Karlitskaya authored
      Add a test case for the new API.
      
      Always check the emulated futex(2) implementation, even on systems with
      futex support.
      40eae351
    • Allison Karlitskaya's avatar
      Bug 548967 - 1 bit mutex lock · 669b0f2d
      Allison Karlitskaya authored
      Add support for a mutex lock that consumes only one bit of storage
      inside of an integer on systems that support futexes.  Futex is emulated
      (at a higher cost) on systems that don't have it -- but only in the
      contended case.
      669b0f2d
  15. 26 Jan, 2010 1 commit
  16. 25 Jan, 2010 1 commit
  17. 18 Jan, 2010 1 commit
  18. 13 Jan, 2010 1 commit
  19. 12 Jan, 2010 1 commit
  20. 07 Jan, 2010 1 commit
  21. 23 Dec, 2009 1 commit
    • Martin Pitt's avatar
      Support storing assertion messages into core dump · da668979
      Martin Pitt authored
      Crash interception/debugging systems like Apport or ABRT capture core dumps for
      later crash analysis. However, if a program exits with an assertion failure,
      the core dump is not useful since the assertion message is only printed to
      stderr.
      
      glibc recently got a patch which stores the message of assert() into the
      __abort_msg global variable.
      (http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=48dcd0ba)
      That works fine for programs which actually use the standard C assert() macro.
      
      This patch adds the same functionality for glib's assertion tests. If we are
      building against a glibc which already has __abort_msg (2.11 and later, or
      backported above git commit), use that, otherwise put it into our own field
      __glib_assert_msg.
      
      Usage:
      
        $ cat test.c
        #include <glib.h>
      
        int main() {
            g_assert(1 < 0);
            return 0;
        }
      
        $ ./test
        **ERROR:test.c:5:main: assertion failed: (1 < 0)
        Aborted (Core dumped)
      
        $ gdb --batch --ex 'print (char*) __abort_msg' ./test core
        [...]
        $1 = 0x93bf028 "ERROR:test.c:5:main: assertion failed: (1 < 0)"
      
      https://bugzilla.gnome.org/show_bug.cgi?id=594872
      da668979
  22. 21 Dec, 2009 1 commit
  23. 14 Dec, 2009 2 commits
  24. 01 Dec, 2009 1 commit
  25. 30 Nov, 2009 1 commit
  26. 28 Nov, 2009 1 commit
  27. 23 Nov, 2009 1 commit
  28. 03 Nov, 2009 1 commit
  29. 07 Oct, 2009 1 commit
  30. 30 Sep, 2009 1 commit
  31. 24 Sep, 2009 2 commits
  32. 22 Sep, 2009 1 commit
  33. 05 Sep, 2009 1 commit