[Asterisk-Users] segmentation fault on asterisk startup
andrewg at felinemenace.org
andrewg at felinemenace.org
Tue Jul 13 05:22:12 MST 2004
Hmm, block is allocated near the top of the stack.
Ack, I don't like the iLBC code for the quick 3 minutes or so I looked at it, but it wouldn't surprise me if it was overwriting more than it should be on the stack.
Well, I'll hand this off to the developers / people who want to spend longer looking over the code (I just happen to be handy with a debugger occasionally).
> #0 0x3aeb0000 in ?? ()
> #1 0x405e2752 in iLBC_encode (bytes=0x810fda0 "? ??\017`\022\021?G\"\214",
> block=0xbffff47c, iLBCenc_inst=0x810e868) at iLBC_encode.c:93
> #2 0x405e0eea in lintoilbc_frameout (tmp=0x810e868) at codec_ilbc.c:196
> #3 0x0805ca2f in calc_cost (t=0x405e9240) at translate.c:238
> #4 0x0805ce4a in ast_register_translator (t=0x405e9240) at translate.c:299
> #5 0x405e0fef in load_module () at codec_ilbc.c:263
> #6 0x080551ce in ast_load_resource (resource_name=0x80defdb
> "codec_ilbc.so")
> at loader.c:312
> #7 0x08055636 in load_modules () at loader.c:407
> #8 0x08084136 in main (argc=2, argv=0xbffffe04) at asterisk.c:1485
> (gdb) x/5i $eip
> 0x3aeb0000: Cannot access memory at address 0x3aeb0000
More information about the asterisk-users
mailing list