| Summary: | ASTERISK-06664: Crash on starting asterisk | ||
| Reporter: | tootai (tootai) | Labels: | |
| Date Opened: | 2006-03-30 10:50:43.000-0600 | Date Closed: | 2011-06-07 14:08:08 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Latest trunk, starting failed with core dump. Here are the last outputs. 1.2.6 start correctly. [...] ASTERISK-367 0x2f6e6962 in ?? () No symbol table info available. ASTERISK-368 0x65747361 in ?? () No symbol table info available. ASTERISK-369 0x6b736972 in ?? () No symbol table info available. ASTERISK-370 0x73752f00 in ?? () No symbol table info available. ASTERISK-371 0x62732f72 in ?? () No symbol table info available. ---Type <return> to continue, or q <return> to quit--- ASTERISK-372 0x612f6e69 in ?? () No symbol table info available. ASTERISK-373 0x72657473 in ?? () No symbol table info available. ASTERISK-374 0x006b7369 in ?? () No symbol table info available. ASTERISK-375 0x00000000 in ?? () No symbol table info available. Cannot access memory at address 0xc0000000 | ||
| Comments: | By: Joshua C. Colp (jcolp) 2006-03-30 11:05:05.000-0600 Yeah that backtrace isn't that helpful... can you rm -rf /usr/lib/asterisk/modules - do a make clean - then a make and make install again? Just to make sure. By: tootai (tootai) 2006-03-30 11:33:02.000-0600 You're right. I install from a empty modules directory and it doesn't core dump. As usually, think twice before to post. Sorry for noise. By: Joshua C. Colp (jcolp) 2006-03-30 11:36:54.000-0600 Problem was with reporter's installation (perhaps version skew...) | ||