[asterisk-bugs] [Asterisk 0016767]: [patch] Deadlock between handle_request_do and do_devstate_changes
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Feb 24 14:24:11 CST 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=16767
======================================================================
Reported By: lmsteffan
Assigned To: dvossel
======================================================================
Project: Asterisk
Issue ID: 16767
Category: Channels/chan_sip/General
Reproducibility: unable to reproduce
Severity: major
Priority: normal
Status: feedback
Asterisk Version: SVN
JIRA: SWP-869
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 238602
Request Review:
======================================================================
Date Submitted: 2010-02-03 20:47 CST
Last Modified: 2010-02-24 14:24 CST
======================================================================
Summary: [patch] Deadlock between handle_request_do and
do_devstate_changes
Description:
title says it all :-)
======================================================================
----------------------------------------------------------------------
(0118508) dvossel (administrator) - 2010-02-24 14:24
https://issues.asterisk.org/view.php?id=16767#c118508
----------------------------------------------------------------------
alright, well that does look odd, but I believe this is the same deadlock
you encountered earlier.
I took by best shot at trying to guess what the problem could based upon
your earlier information and that did not appear to work. Lets try
something different. Next time this deadlock occurs I need you to gather
some gdb information for me.
Run 'make menuselect' and make sure you are compiling with DON'T OPTIMIZE
enabled under compile flags. Recompile if necessary, then the next time
this deadlock occurs attach gdb to the process and give me the "thread
apply all bt" and "thread apply all bt full" output. You can attach gdb to
asterisk using gdb `pidof asterisk`
Without the gdb output I am just guessing at this point.
Issue History
Date Modified Username Field Change
======================================================================
2010-02-24 14:24 dvossel Note Added: 0118508
======================================================================
More information about the asterisk-bugs
mailing list