Enable some relatively expensive debugging checks in Libevent that
would normally be turned off. Generally, these checks cause code that
would otherwise crash mysteriously to fail earlier with an assertion
failure. Note that this method MUST be called before any events or
event_bases have been created.
Debug mode can currently catch the following errors:
An event is re-assigned while it is added
Any function is called on a non-assigned event
Note that debugging mode uses memory to track every event that has been
initialized (via event_assign, event_set, or event_new) but not yet
released (via event_free or event_debug_unassign). If you want to use
debug mode, and you find yourself running out of memory, you will need
to use event_debug_unassign to explicitly stop tracking events that
are no longer considered set-up.
Enable some relatively expensive debugging checks in Libevent that would normally be turned off. Generally, these checks cause code that would otherwise crash mysteriously to fail earlier with an assertion failure. Note that this method MUST be called before any events or event_bases have been created.
Debug mode can currently catch the following errors: An event is re-assigned while it is added Any function is called on a non-assigned event
Note that debugging mode uses memory to track every event that has been initialized (via event_assign, event_set, or event_new) but not yet released (via event_free or event_debug_unassign). If you want to use debug mode, and you find yourself running out of memory, you will need to use event_debug_unassign to explicitly stop tracking events that are no longer considered set-up.
@see event_debug_unassign()