[asterisk-bugs] [Asterisk 0017355]: Possible crash in astobj2

[Asterisk Bug Tracker]

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:                     feedback
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 10:00 CDT
====================================================================== 
Summary:                    Possible crash in astobj2
Description: 
I will upload the traces in 1 minute
====================================================================== 

---------------------------------------------------------------------- 
 (0122145) lmadsen (administrator) - 2010-05-19 10:00
 https://issues.asterisk.org/view.php?id=17355#c122145 
---------------------------------------------------------------------- 
Now for this issue in particular, here is some information from IRC:

<putnopvut> leifmadsen: yikes @ that crash. It's a weirdo memory
corruption issue so it's not easy to determine if it's still present in
1.6.2 or not. I would be safe and assume it is a problem there, though.

<leifmadsen> ok sounds good -- what other information should I request
from him?

<putnopvut> leifmadsen: sorry, missed your question earlier. valgrind
would be cool if he's willing.

<leifmadsen> is the backtrace useful enough on its own?
<leifmadsen> if valgrind information is necessary though, that might be
more difficult to debug then

<putnopvut> leifmadsen: well, valgrind would be ideal. Otherwise, the way
that it would have to be done is to comb through chan_sip and try to figure
out possible ways that a bad dialog could get into the dialog container.

<putnopvut> And honestly, I think that's close to impossible.


So to summarize, valgrind output is probably necessary to move this issue
forward. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-19 10:00 lmadsen        Note Added: 0122145                          
======================================================================