| Summary: | ASTERISK-13467: crash with asterisk realtime running odbc -> sql 2008 server via freetds when snom 190 reboots cached realtime | ||
| Reporter: | Kamil Czajko (kactus) | Labels: | |
| Date Opened: | 2009-01-27 22:12:37.000-0600 | Date Closed: | 2011-06-07 14:01:01 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Resources/res_odbc |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) asterisk_cli_output.txt ( 1) backtrace.txt ( 2) malloc_debug.txt ( 3) valgrind.txt | |
| Description: | Hello Everyone I've recently come back to testing asterisk 1.6 and I've stopped short once again. In this simple case I have two snom phones setup with sip accounts in a mssql db.I start the asterisk server, and can sometimes reregister the snom 320 so that it appears under sip show peers, but hitting reregister (on the phone) a few times, or having a snom 190 reboot, thus unregister and reregister causes a segmentation fault. I have both a username field and a defaultuser field in the table (to try and get around the warning), but that still shouldn't cause a segfault. I will upload debug and cli output momentarily I had similar issue with 1.6.0.5 All the best | ||
| Comments: | By: Kamil Czajko (kactus) 2009-01-27 22:23:31.000-0600 I should probably also mention that installing 1.4.17 with same configs works without issue. By: Tilghman Lesher (tilghman) 2009-01-27 23:08:06.000-0600 Please follow the instructions in doc/valgrind.txt. By: Kamil Czajko (kactus) 2009-01-28 00:21:03.000-0600 Hello Corydon The system did not crash when running valgrind but I have uploaded the logs anyway. There are invalid reads there in the log so hopefully that will help. I retested without valgrind and it seg faulted straight away. Let me know if you need anything else. By: Tilghman Lesher (tilghman) 2009-01-28 01:18:57.000-0600 This needs to be reported to the FreeTDS project. Use the same valgrind output. This is a double-free error within their own software. By: Kamil Czajko (kactus) 2009-01-28 23:20:28.000-0600 Hello Corydon Thank you for your help. I had been running freetds 0.64 (lastest from yum on centos 5.2) I have since retested with 0.84 built from source and the crash does not occur. I get a mass of sip debugs but that is another story. It is still strange that is does not crash under 1.4.17 but at least I now have something I can move forward with. Once again thank you for your help. Kamil By: Tilghman Lesher (tilghman) 2009-01-28 23:28:23.000-0600 Resolved with FreeTDS upgrade | ||