libust: New transport mutex v2

[ust.git] / libust / marker.c

diff --git a/libust/marker.c b/libust/marker.c
index 788d87691beb0ddc6fd4f51efb2df7cad151545c..96d140996890c40c5b4a43da45a63a4180aad7d3 100644 (file)
--- a/libust/marker.c
+++ b/libust/marker.c
@@ -693,20 +693,6 @@ void marker_update_probe_range(struct marker * const *begin,
                        /*
                         * ignore error, continue
                         */
-
-                       /* This is added for UST. We emit a core_marker_id event
-                        * for markers that are already registered to a probe
-                        * upon library load. Otherwise, no core_marker_id will
-                        * be generated for these markers. Is this the right thing
-                        * to do?
-                        */
-                       trace_mark(metadata, core_marker_id,
-                                  "channel %s name %s event_id %hu "
-                                  "int #1u%zu long #1u%zu pointer #1u%zu "
-                                  "size_t #1u%zu alignment #1u%u",
-                                  (*iter)->channel, (*iter)->name, mark_entry->event_id,
-                                  sizeof(int), sizeof(long), sizeof(void *),
-                                  sizeof(size_t), ltt_get_alignment());
                } else {
                        disable_marker(*iter);
                }
@@ -1387,8 +1373,7 @@ lib_added:
        /* FIXME: update just the loaded lib */
        lib_update_markers();
 
-       /* markers_count - 1: skip dummy */
-       DBG("just registered a markers section from %p and having %d markers", markers_start, markers_count - 1);
+       DBG("just registered a markers section from %p and having %d markers (minus dummy markers)", markers_start, markers_count);
        
        return 0;
 }