Summary: | ASTERISK-01233: segmentation fault | ||
Reporter: | senad (senad) | Labels: | |
Date Opened: | 2004-03-17 08:38:19.000-0600 | Date Closed: | 2004-09-25 02:53:49 |
Priority: | Critical | Regression? | No |
Status: | Closed/Complete | Components: | Core/NewFeature |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | Hi, It all worked fine this morning with bindaddr=0.0.0.0 then suddenly it wont start unless bindaddr=$IP ADDRESS. This is relating to sip.conf. I have changed many fields in sip.conf this morning before this started happening, but segmantation fault was prabably triggered setting allow=iLBC in general section. | ||
Comments: | By: zoa (zoa) 2004-03-17 08:40:59.000-0600 what version are you running ? did you also upgrade this morning ? By: senad (senad) 2004-03-17 09:06:42.000-0600 I am Running DEV CVS-03/13/04-21:45:03. No, i did not upgrade this morning.. Also.. this sort of problem I have experinced before( Aug 2003). By: Mark Spencer (markster) 2004-03-19 01:07:59.000-0600 Can we see a backtrace of your segfault? By: senad (senad) 2004-03-19 15:52:02.000-0600 never done that before... any instructions somewhere on how to do that? By: Mark Spencer (markster) 2004-03-19 16:23:08.000-0600 join #asterisk on irc.freenode.net and get a bug marshal to help you with the backtrace. By: senad (senad) 2004-03-20 05:49:21.000-0600 ok.. i found what the cause of the problem is: I have been running * as non root user ;).... Now that i changed it to root, all is fine. I must leave this server working as it is (root), so i will configure another server in non root mode in order to try to replicate the problem and then I will send you backtrace. By: Olle Johansson (oej) 2004-03-20 08:23:32.000-0600 Wonder if this is related to 0001258? By: senad (senad) 2004-03-20 14:40:12.000-0600 well... mark has fixed 0001258.... so.. YES, prabably it is related. I will though keep an eye on this issue... By: Mark Spencer (markster) 2004-03-20 14:40:24.000-0600 This is the same bug about the routing table. |