1. 06 Jun, 2010 10 commits
  2. 05 Jun, 2010 1 commit
  3. 04 Jun, 2010 6 commits
  4. 03 Jun, 2010 5 commits
  5. 02 Jun, 2010 5 commits
  6. 30 May, 2010 3 commits
  7. 29 May, 2010 1 commit
  8. 28 May, 2010 5 commits
  9. 27 May, 2010 4 commits
    • Alexander Larsson's avatar
      Add dtrace and systemtap support for gobject · 8e41be13
      Alexander Larsson authored
      This adds static markers and systemtap tapsets for:
      
      * type creation
      * object lifetimes (creation, ref, unref, dispose, finalize)
      * signal creation and emission
      
      Signal emissions and finalization marker have a corresponding
      *_end (or *-end in dtrace) version that is when the corresponding
      operation is finished.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=606044
      8e41be13
    • Alexander Larsson's avatar
      Initial support for dtrace and systemtap · bef9efd0
      Alexander Larsson authored
      This adds static markers for dtrace, which are also usable
      by systemtap. Additionally it adds a tapset for systemtap
      that makes it easier to use the static markers.
      
      These are enabled by default.
      
      This initial set of probes is rather limited:
      
      * allocation and free using g_malloc & co
      * allocation and free using g_slice
      * gquark name tracking (useful for converting quarks to strings in probes)
      
      Notes on naming:
      
      Its traditional with dtrace to use probe names with dashes as
      delimiter (slice-alloc). Since dashes are not usable in identifiers
      the C code uses double underscores (slice__alloc) which is converted
      to dashes in the UI. We follow this for the shared lowlevel probe
      names.
      
      Additionally dtrace supports putting a "provider" part in the probe
      names which is essentially a namespacing thing. On systemtap this
      field is currently ignored (but may be implemented in the future), but
      this is not really a problem since in systemtap the probes are
      specified by combining the solib file and the marker name, so there
      can't really be name conflicts.
      
      For the systemtap tapset highlevel probes we instead use names that
      are systemtapish with single dashes as separators.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=606044
      bef9efd0
    • Mikhail Zabaluev's avatar
      Optimized the overlong sequence check in g_utf8_get_char_extended() · c3bc0f4f
      Mikhail Zabaluev authored
      Rather make it branch to get the due sequence length for the resulting
      character code, we can as well get the minimum code value in the initial
      branching.
      c3bc0f4f
    • Allison Karlitskaya's avatar
      GSettings schema docs: mention need for EXTRA_DIST · 30a85629
      Allison Karlitskaya authored
      Mention that you will need to use EXTRA_DIST for your schema file if it
      is distributed with your project.
      30a85629