From: Juan Carlos Castro y Castro <jcastro@instant.com.br>
To: alsa-devel@lists.sourceforge.net
Subject: What happened with the DEBUG_THREAD define in the asterisk Makefile?
Date: Tue, 23 May 2006 17:28:26 -0300 [thread overview]
Message-ID: <4473706A.3020305@instant.com.br> (raw)
There's no mention of it in the current SVN version. Version 1.2.7.1 had
the following:
# Optional debugging parameters
DEBUG_THREADS = #-DDUMP_SCHEDULER #-DDEBUG_SCHEDULER #-DDEBUG_THREADS
#-DDO_CRASH #-DDETECT_DEADLOCKS
Also, the "howto debug a deadlock" at
http://www.voip-info.org/wiki/view/Asterisk+debugging seems to be out of
date -- it doesn't tell what DUMP_SCHEDULER, DEBUG_SCHEDULER and
DETECT_DEADLOCKS are for, how can they be used, or what caveats are
associated with enabling them.
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
next reply other threads:[~2006-05-23 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 20:28 Juan Carlos Castro y Castro [this message]
2006-05-23 21:23 ` SORRY all! Juan Carlos Castro y Castro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4473706A.3020305@instant.com.br \
--to=jcastro@instant.com.br \
--cc=alsa-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.