[asterisk-bugs] [Asterisk 0017355]: I capture the trace but cannot tell what part of the code is blowing up
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed May 19 09:33:56 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17355
======================================================================
Reported By: falves11
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17355
Category: Core/General
Reproducibility: random
Severity: crash
Priority: normal
Status: new
Asterisk Version: 1.6.1 - SECURITY ONLY! Test 1.6.2
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1
SVN Revision (number only!): 262802
Request Review:
======================================================================
Date Submitted: 2010-05-18 17:30 CDT
Last Modified: 2010-05-19 09:33 CDT
======================================================================
Summary: I capture the trace but cannot tell what part of the
code is blowing up
Description:
I will upload the traces in 1 minute
======================================================================
----------------------------------------------------------------------
(0122138) lmadsen (administrator) - 2010-05-19 09:33
https://issues.asterisk.org/view.php?id=17355#c122138
----------------------------------------------------------------------
The first issue I looked at is https://issues.asterisk.org/view.php?id=17248
which had a patch posted for you to
test and there is no feedback from you about the result or an
acknowledgement that you are going to test it.
The second issue, https://issues.asterisk.org/view.php?id=17264 will likely get
looked at in the next sprint
session.
Issue https://issues.asterisk.org/view.php?id=15464 will get looked at as soon
as time and resources allow.
The last issue https://issues.asterisk.org/view.php?id=17084 you have already
acknowledged it works for you and
will be looked at by a developer as soon as time and resources allow. You
could also port that forward and apply it against the 1.6.2 branch. I'm
guessing it would apply with only minor adjustments.
However, for this issue in particular we are going to close this issue.
Your inability to move to 1.6.2 still does not move us from the fact that
1.6.1 is only supported for security fixes, and that issues need to be able
to reproduce on the 1.6.2 branch in order to move bugs forward.
Issue History
Date Modified Username Field Change
======================================================================
2010-05-19 09:33 lmadsen Note Added: 0122138
======================================================================
More information about the asterisk-bugs
mailing list