mirror of
https://github.com/alsa-project/alsa-lib.git
synced 2025-10-29 05:40:25 -04:00
Change assert condition in error message handler
Activating assert() in the default error message handler isn't always good for producitve systems. Make this optional and enable only when a special configure option is given (i.e. for explicit debugging).
This commit is contained in:
parent
d6093c58f3
commit
631f7cde82
3 changed files with 23 additions and 3 deletions
7
NOTES
7
NOTES
|
|
@ -27,12 +27,15 @@ LIBASOUND_DEBUG is set (to a non-empty value).
|
|||
When LIBASOUND_DEBUG=1 is set, the errors in hw_params configuration
|
||||
will be dumped to stderr. Note that this will show even the non-fatal
|
||||
errors of plug layer (trial-and-error of parameters).
|
||||
When LIBASOUND_DEBUG=2 is set, the default error message handler calls
|
||||
assert() to catch with a debugger, in addition to parameter debugging.
|
||||
|
||||
This feature is disabled when --with-debug=no is passed to configure,
|
||||
i.e. no strict checking is done in alsa-lib.
|
||||
|
||||
In addition, when --enable-debug-assert configure option is given and
|
||||
when LIBASOUND_DEBUG_ASSERT=1 is set, the default error message
|
||||
handler can call assert() to catch with a debugger. This feature was
|
||||
formerly activated via LIBASOUND_DEBUG=2.
|
||||
|
||||
|
||||
Blocking Open Mode
|
||||
==================
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue