diff options
| author | Havoc Pennington <hp@redhat.com> | 2006-10-17 20:52:13 +0000 |
|---|---|---|
| committer | Havoc Pennington <hp@redhat.com> | 2006-10-17 20:52:13 +0000 |
| commit | f1ca9b89e92de4d876dc5e7e85710c4d2dc87638 (patch) | |
| tree | 4f52c7303bd028114da11e6a8d212d4059ad2570 /dbus/dbus-dataslot.c | |
| parent | c4b5ea1b95f5c14fb9f51e51367d7bc9201e8b71 (diff) | |
2006-10-17 Havoc Pennington <hp@redhat.com>
* dbus/dbus-internals.c (_dbus_warn_check_failed): new function to
be used for return_if_fail type warnings; prefixes the pid, and
fatal by default.
Diffstat (limited to 'dbus/dbus-dataslot.c')
| -rw-r--r-- | dbus/dbus-dataslot.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/dbus/dbus-dataslot.c b/dbus/dbus-dataslot.c index f9c12f84..3e9aabfc 100644 --- a/dbus/dbus-dataslot.c +++ b/dbus/dbus-dataslot.c @@ -79,7 +79,7 @@ _dbus_data_slot_allocator_alloc (DBusDataSlotAllocator *allocator, } else if (allocator->lock_loc != mutex_loc) { - _dbus_warn ("D-Bus threads were initialized after first using the D-Bus library. If your application does not directly initialize threads or use D-Bus, keep in mind that some library or plugin may have used D-Bus or initialized threads behind your back. You can often fix this problem by calling dbus_init_threads() or dbus_g_threads_init() early in your main() method, before D-Bus is used."); + _dbus_warn_check_failed ("D-Bus threads were initialized after first using the D-Bus library. If your application does not directly initialize threads or use D-Bus, keep in mind that some library or plugin may have used D-Bus or initialized threads behind your back. You can often fix this problem by calling dbus_init_threads() or dbus_g_threads_init() early in your main() method, before D-Bus is used.\n"); _dbus_assert_not_reached ("exiting"); } |