[asterisk-bugs] [Asterisk 0015351]: Segfault on agent login, with manager, agi and pgsql realtime
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Nov 11 09:25:53 CST 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=15351
======================================================================
Reported By: fiddur
Assigned To: mnicholson
======================================================================
Project: Asterisk
Issue ID: 15351
Category: Resources/res_config_pgsql
Reproducibility: always
Severity: crash
Priority: normal
Status: feedback
Target Version: 1.6.1.11
Asterisk Version: SVN
JIRA: SWP-320
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-06-18 03:47 CDT
Last Modified: 2009-11-11 09:25 CST
======================================================================
Summary: Segfault on agent login, with manager, agi and pgsql
realtime
Description:
Asterisk segfaults on agent login. In our scenario, the following
happens:
1. User calls 200
2. agi-script login.pl performs:
1. takes an id through application Read.
2. When login succeeds, it inserts into realtime table
queue_member_table
3. reads the variable QUEUE_MEMBER($queue) for each queue the agent is
inserted into
4. sends a UserEvent.
3. The UserEvent is catched by the manager:
1. It pauses the queuemember via QueuePause.
The crash won't happen if the manager doesn't send the QueuePause
command.
This works well in 1.6.0
The crash happens in svn trunk too.
======================================================================
----------------------------------------------------------------------
(0113654) fiddur (reporter) - 2009-11-11 09:25
https://issues.asterisk.org/view.php?id=15351#c113654
----------------------------------------------------------------------
It works well in trunk r229431 now, great! I don't know what version I
tried in, but i tested latest trunk a couple of times. ...don't know why I
didn't give the revision id on reporting...
Issue History
Date Modified Username Field Change
======================================================================
2009-11-11 09:25 fiddur Note Added: 0113654
======================================================================
More information about the asterisk-bugs
mailing list