| Summary: | ASTERISK-12759: Last 1.4 svn crash. Backtrace attached | ||
| Reporter: | Badalian Vyacheslav (slavon) | Labels: | |
| Date Opened: | 2008-09-20 07:04:53 | Date Closed: | 2011-06-07 14:00:37 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | CDR/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) gdb.txt ( 1) valgrind.txt | |
| Description: | Hello all. Last 1.4 svn crash. Backtrace and valgrind attached Thanks | ||
| Comments: | By: Badalian Vyacheslav (slavon) 2008-09-20 07:06:47 Revision 143736 By: Badalian Vyacheslav (slavon) 2008-09-20 07:08:49 Related to 0013490 but with valgrind test.... By: Steve Murphy (murf) 2008-09-25 17:56:21 Many bug fixes have been committed since you entered this bug. If you could check out the latest 1.4 from svn, and compile and test that in your environment, we can determine if we still have a bug or not! By: Steve Murphy (murf) 2008-10-13 18:32:02 slavon-- This bug has been in feedback mode for a while. I shall probably give it another day, and close it with status "suspended", and you'll be able to re-open it when you have more info. I have tried to reproduce the valgrind results you reported, but with blind xfers, it did not have any problems. The gdb stack trace reports a crash in the sip channel driver, the valgrind report memory errors in specialized_reset, but I need to know exactly what kind of xfer gave these results! By: Leif Madsen (lmadsen) 2008-10-14 11:06:22 I'm going to suspend this issue, but please feel free to reopen it when you have some additional information. Please test with latest version of 1.4 from SVN if possible to determine if the issue still exists. If it does, of course please reopen the issue with that new info! Thanks! | ||