| Summary: | ASTERISK-07950: Segmentation fault with mysql realtime | ||
| Reporter: | flavio patria (obelix_it) | Labels: | |
| Date Opened: | 2006-10-18 06:58:16 | Date Closed: | 2007-04-02 10:03:54 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Core/Configuration |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) bt_1.2.13.txt ( 1) bt_full_ast1.2.13.txt ( 2) bt_full_complete.1.2.13.txt ( 3) bt_full_segmentation_fault.txt | |
| Description: | As suggested in asterisk-dev list I post here my issue. I've a segmentation fautl error when using realtime module, with mysql as db. I've observed that problem always occurs: - when an UA, stored in my mysql asterisk db (as friend), send sip message register to Asterisk - for both incoming and outgoing calls with UA stored in my mysql asterisk db. Asterisk is connected to mysql asterisk db successfully. ****** ADDITIONAL INFORMATION ****** I've attached gdb backtrace with the "full" option turned on. mysql version is 4.1.10a-standard | ||
| Comments: | By: Serge Vecher (serge-v) 2006-10-23 13:43:31 are things any different with 1.2.13? By: flavio patria (obelix_it) 2006-10-24 05:05:19 Sobh, nothing different!! :( I've recompiled asterisk with release 1.2.13 typing "make clean", "make" and "make install". Then I've recompiled asterisk addons too. Anyway segmentation fault errors occoures just like previous rel. I've attached new gdb core dump related to asterisk version 1.12.3. I'hope this may be helpfully. By: inspired (inspired) 2006-10-24 05:08:03 Are you perhaps storing CDR in ODBC at the same time? I used to get segmentation faults at random times when I used MySQL and ODBC together. By: flavio patria (obelix_it) 2006-10-24 05:32:49 No, I do not use ODBC. I use only mysql db in order to storage my sip peers(friends). By: Serge Vecher (serge-v) 2006-10-26 09:16:18 forgot to mention, that you need to built asterisk with "make don-optimize" in order for compiler optimizations to be turned off (so that the bt is useful to developers). By: flavio patria (obelix_it) 2006-10-30 10:12:31.000-0600 I've recompiled and installed asterisk 1.2.13 (with don-optimize make option) and recompiled asterisk addons 1.2.5: segmentation fault errors still occoures. I've attached new gdb bt full trace (named bt_1.2.13.txt) I'hope this may be helpfully. Thanks 4 support By: Anthony LaMantia (alamantia) 2006-10-31 16:04:37.000-0600 are you positive these backtraces are being copied from the right position. the stack dump should increment from #0 the most recent frame to .... #n By: flavio patria (obelix_it) 2006-11-02 05:41:28.000-0600 So, I did copy and paste most significant part for stack dump trace. Do you need complete stack dump in order to fix? If so, I'll put it!! Thanks for all By: flavio patria (obelix_it) 2006-11-07 11:17:45.000-0600 In the end..I've attached bt_full_complete.1.2.13.txt,a complete stack dump. I'hope this may be helpfully. Thanks By: Serge Vecher (serge-v) 2007-03-30 10:04:08 Obelix_IT: has there been any changes to this, have you resolved this issue? By: flavio patria (obelix_it) 2007-04-02 02:23:26 serge-v - manager: No.I did workaround it upgrading my asterisk to 1.2.16. By: Serge Vecher (serge-v) 2007-04-02 10:03:54 well, if an older release does not have a problem of an earlier one, then it's a fix, not a workaround ;) Thanks for reporting back. If this reappears again in the latest asterisk release, please reopen the issue with a new backtrace. | ||