| Summary: | ASTERISK-19062: app_stack: cannot access memory at address 0x0 | ||||
| Reporter: | Ovidiu Sas (ovi) | Labels: | |||
| Date Opened: | 2011-12-18 12:05:06.000-0600 | Date Closed: | 2011-12-19 12:33:43.000-0600 | ||
| Priority: | Minor | Regression? | |||
| Status: | Closed/Complete | Components: | Applications/app_stack | ||
| Versions: | 1.8.8.0 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | Asterisk running on embedded platform (Linksys NSLU2): Linux LKG7CAC92 2.4.22-xfs #1 Sat Dec 29 03:29:38 UTC 2007 armv5b GNU/Linux | Attachments: | |||
| Description: | gdb) bt #0 0xc1d57850 in ?? () #1 0x40720298 in ?? () from /opt/lib/asterisk/modules/app_stack.so Cannot access memory at address 0x0 I don't have debug symbols on this platform. | ||||
| Comments: | By: Leif Madsen (lmadsen) 2011-12-18 19:53:28.125-0600 Well there are no changes in app_stack.so between 1.8.7.0-rc1 and now in the 1.8 branch, and you had mentioned via IM that you were not experiencing this on 1.8.7.0, but are on 1.8.8.0 -- so unfortunately additional information is going to have to be provided for this issue to progress forward. By: Ovidiu Sas (ovi) 2011-12-18 23:34:04.509-0600 I recompiled with debug symbols but I don't get much more: Core was generated by `asterisk -Tg'. Program terminated with signal 4, Illegal instruction. [New process 951] #0 0xbfffc80c in ?? () (gdb) bt #0 0xbfffc80c in ?? () Cannot access memory at address 0x0 As soon as I add: noload => app_stack.so to modules.conf, everything is working properly ... By: David Woolley (davidw) 2011-12-19 06:01:42.384-0600 The illegal instruction error is the real error. The headline error is from gdb, not the program. Either you are using binaries unsuited to the platform, or there has been major corruption of memory. Crashes at load time are usually due to leaving modules from older versions in the modules directory. By: Ovidiu Sas (ovi) 2011-12-19 08:24:07.363-0600 > Either you are using binaries unsuited to the platform, or there has been major corruption of memory. If I don't load app_stack.so, everything is working ok. I can attach to the main asterisk program with gdb: (gdb) bt #0 0x4020d814 in poll () from /lib/libc.so.6 #1 0x0003f370 in monitor_sig_flags (unused=0xfffffffc) at asterisk.c:3094 #2 0x00038310 in main (argc=11, argv=0xbffffe14) at asterisk.c:3912 Since asterisk is working ok without the app_stack.so, I don't think that I have memory issues. > Crashes at load time are usually due to leaving modules from older versions in the modules directory. Also, the install process is package based and it is used to install hundreds of packages. When an install or upgrade is performed, everything is taken from a package (just to avoid any issues related to leftover files from other packages). I will do some more investigations, but if you guys have any other ideas about how can I investigate this particular issue, I would really appreciate sharing them. By: Richard Mudgett (rmudgett) 2011-12-19 11:46:03.249-0600 I think this is really a duplicate of ASTERISK-18728. By: Leif Madsen (lmadsen) 2011-12-19 12:33:43.346-0600 I'm closing this as a duplicate of an existing issue per Richard. | ||||