diff options
| author | John (J5) Palmieri <johnp@redhat.com> | 2006-08-14 19:33:20 +0000 |
|---|---|---|
| committer | John (J5) Palmieri <johnp@redhat.com> | 2006-08-14 19:33:20 +0000 |
| commit | 5b5da5297552919578266714fa7abf1e45d1131d (patch) | |
| tree | 5d64b3b3bb7036e073f8a9403360e79961730b44 /dbus | |
| parent | c1091cbbd2477699dc16f8c8e3d15fea2f68d603 (diff) | |
* dbus/dbus-dataslot.c (_dbus_data_slot_allocator_alloc):
Change _dbus_abort to _dbus_assert_not_reached because _dbus_abort
causes compile problems when asserts are turned off
Keeping _dbus_warn for printing out the message so even if
asserts are turned off the user gets the messages that something is
wrong
Diffstat (limited to 'dbus')
| -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 83e25865..78e94c37 100644 --- a/dbus/dbus-dataslot.c +++ b/dbus/dbus-dataslot.c @@ -81,7 +81,7 @@ _dbus_data_slot_allocator_alloc (DBusDataSlotAllocator *allocator, else if (allocator->lock != mutex) { _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_abort (); + _dbus_assert_not_reached ("exiting"); } if (*slot_id_p >= 0) |