[asterisk-bugs] [Asterisk 0013380]: [patch] pthread_cancel segmentation faults
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Aug 27 14:19:19 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=13380
======================================================================
Reported By: Matti
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 13380
Category: Channels/chan_h323
Reproducibility: always
Severity: minor
Priority: normal
Status: feedback
Asterisk Version: 1.2.X
SVN Branch (only for SVN checkouts, not tarball releases): 1.2
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2008-08-27 01:20 CDT
Last Modified: 2008-08-27 14:19 CDT
======================================================================
Summary: [patch] pthread_cancel segmentation faults
Description:
pthread_cancel segmentation faults when the bind address in h323.conf is
not configured in Linux. A detached thread must not be cancelled.
======================================================================
----------------------------------------------------------------------
(0091831) Corydon76 (administrator) - 2008-08-27 14:19
http://bugs.digium.com/view.php?id=13380#c91831
----------------------------------------------------------------------
That's a nice message asserting that it is so, but I don't know of any real
documentation that detached threads are non-cancellable. In fact, the
documentation of pthread_cancel both on the manpage, as well as in the
POSIX specification make no such restriction on the use of pthread_cancel.
So I'm puzzled as to where that bare assertion came from.
In fact, we cancel other detached threads in Asterisk with no problem at
all. So I think you're finding the wrong solution to the stated problem,
and we need to find the real reason this is crashing. Do you have a
backtrace, perhaps? I've noted in another place recently that there is a
possible race when a thread is created and destroyed in the same context
switch, although that is probably not happening here.
Issue History
Date Modified Username Field Change
======================================================================
2008-08-27 14:19 Corydon76 Note Added: 0091831
======================================================================
More information about the asterisk-bugs
mailing list