-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, After upgrading the kernel on an Asterisk box, asterisk segfaults on startup. It seems like it's the g729 codec that causes this: #0 0x4015acad in memset () from /lib/libc.so.6 #1 0x4022686a in load_module () at codec_g729b.c:416 #2 0x08054794 in ast_load_resource (resource_name=0x80d1068 "codec_g729b.so") at loader.c:298 #3 0x08054de3 in load_modules () at loader.c:344 #4 0x0807de5e in main (argc=-1073748912, argv=0x1) at asterisk.c:1398 #5 0x400f4bb4 in __libc_start_main () from /lib/libc.so.6 What did I miss? - -- Regards, Tais M. Hansen ComX Networks Tel: +45-70257474 Fax: +45-70257374 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/VaYE2TEAILET3McRAh8yAJ4h0d8ywMUE2LMT8AB5Ber/2UBU7QCeOA36 rMLOqtIQHWg374TPu10TDX0=Ri9s -----END PGP SIGNATURE-----
Try the new_codec_binary/codec_g729b.so from our ftp site. regards Martin On Wed, 3 Sep 2003, Tais M. Hansen wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > After upgrading the kernel on an Asterisk box, asterisk segfaults on startup. > It seems like it's the g729 codec that causes this: > > #0 0x4015acad in memset () from /lib/libc.so.6 > #1 0x4022686a in load_module () at codec_g729b.c:416 > #2 0x08054794 in ast_load_resource (resource_name=0x80d1068 "codec_g729b.so") > at loader.c:298 > #3 0x08054de3 in load_modules () at loader.c:344 > #4 0x0807de5e in main (argc=-1073748912, argv=0x1) at asterisk.c:1398 > #5 0x400f4bb4 in __libc_start_main () from /lib/libc.so.6 > > What did I miss? > > - -- > Regards, > Tais M. Hansen > ComX Networks > Tel: +45-70257474 > Fax: +45-70257374 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.2 (GNU/Linux) > > iD8DBQE/VaYE2TEAILET3McRAh8yAJ4h0d8ywMUE2LMT8AB5Ber/2UBU7QCeOA36 > rMLOqtIQHWg374TPu10TDX0> =Ri9s > -----END PGP SIGNATURE----- > > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users >
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 03 September 2003 16:37, Martin Pycko wrote:> Try the new_codec_binary/codec_g729b.so from our ftp site.Yes, sir! :) ... Sadly, that one also segfaults: (gdb) bt #0 0x4015acad in memset () from /lib/libc.so.6 #1 0x40226bea in load_module () at codec_g729b.c:514 #2 0x08054794 in ast_load_resource (resource_name=0x80d1098 "codec_g729b.so") at loader.c:298 #3 0x08054de3 in load_modules () at loader.c:344 #4 0x0807de5e in main (argc=-1073747744, argv=0x1) at asterisk.c:1398 #5 0x400f4bb4 in __libc_start_main () from /lib/libc.so.6 Does it require anything in the kernel that I might accidently have switched off? - -- Regards, Tais M. Hansen ComX Networks Tel: +45-70257474 Fax: +45-70257374 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/VgbE2TEAILET3McRArDHAKCjl2pfaC4cucxbJb4mo7SpgtXEUACfUlIS 6OwRFDLExz2K5bqmmIUf4io=E5UH -----END PGP SIGNATURE-----
On Wed, 2003-09-03 at 10:20, Tais M. Hansen wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Wednesday 03 September 2003 16:37, Martin Pycko wrote: > > Try the new_codec_binary/codec_g729b.so from our ftp site. > > Yes, sir! :) > > ... Sadly, that one also segfaults: > > (gdb) bt > #0 0x4015acad in memset () from /lib/libc.so.6 > #1 0x40226bea in load_module () at codec_g729b.c:514 > #2 0x08054794 in ast_load_resource (resource_name=0x80d1098 "codec_g729b.so") > at loader.c:298 > #3 0x08054de3 in load_modules () at loader.c:344 > #4 0x0807de5e in main (argc=-1073747744, argv=0x1) at asterisk.c:1398 > #5 0x400f4bb4 in __libc_start_main () from /lib/libc.so.6 > > Does it require anything in the kernel that I might accidently have switched > off?I wonder if you are having a libc problem. Recently my workstation started having problems with a couple of apps and libc. I did track it down to a recent update I had done, and then about a few days ago debian released another libc update and all is fine again.>From your backtrace, either libc is doing something wrong, or theload_module is not validating that malloc was successful, or passing an incorrect value to memset. -- Steven Critchfield <critch@basesys.com>