On Thu, Feb 23, 2006 at 01:21:40PM +0100, Sander Hoentjen wrote: > On Wed, 2006-02-22 at 12:53 +0100, tjikkun@xxxxxxxxx wrote: > > > On Wed, Feb 22, 2006 at 09:01:16AM +0100, Sander Hoentjen wrote: > > >> On Tue, 2006-02-21 at 14:39 +0100, Sander Hoentjen wrote: > > >> > > > >> > http://dl.atrpms.net/fc5-i386/atrpms/stable/ > > >> > that is the location i have in my atrpm.repo > > >> > I can see asterisk-1.2.4-18.rhfc4.92.at.i386.rpm but no zaptel > > >> > whatsoever > > >> > > > >> Ok now there i zaptel and I installed it. > > > > > > Yes, I had forgotten to flag zaptel on FC5 as finished, so the build > > > system would not grab it and place it into the public repo. > > > > > >> Next step: learn how to configure asterisk :) > > > > > > Have fun ... ;) > > The fun starts with a segfault runing /usr/sbin/asterisk -d > > If you have any pointers on how to troubleshoot this I would greatly > > appreciate it. I am not at home at the moment so I probably won't be able > > to try anything before tomorrow. > > > > Sander > > > # gdb --args /usr/sbin/asterisk -d > GNU gdb Red Hat Linux (6.3.0.0-1.98.2rh) > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you > are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for > details. > This GDB was configured as "i386-redhat-linux-gnu"...(no debugging > symbols found) > Using host libthread_db library "/lib/libthread_db.so.1". > > (gdb) run > Starting program: /usr/sbin/asterisk -d > Reading symbols from shared object read from target memory...(no > debugging symbols found)...done. > Loaded system supplied DSO at 0xdf4000 > (no debugging symbols found) > (no debugging symbols found) > (no debugging symbols found) > [Thread debugging using libthread_db enabled] > [New Thread -1208162640 (LWP 32098)] > (no debugging symbols found) > (no debugging symbols found) > (no debugging symbols found) > (no debugging symbols found) > (no debugging symbols found) > (no debugging symbols found) > (no debugging symbols found) > (no debugging symbols found) > (no debugging symbols found) > (no debugging symbols found) > (no debugging symbols found) > (no debugging symbols found) > [New Thread -1208165472 (LWP 32101)] > [Thread -1208165472 (LWP 32101) exited] > [New Thread -1208165472 (LWP 32102)] > [New Thread -1208431712 (LWP 32103)] > (no debugging symbols found) > [New Thread -1208697952 (LWP 32104)] > (no debugging symbols found) > (no debugging symbols found) > (no debugging symbols found) > (no debugging symbols found) > (no debugging symbols found) > (no debugging symbols found) > (no debugging symbols found) > (no debugging symbols found) > (no debugging symbols found) > (no debugging symbols found) > (no debugging symbols found) > [New Thread -1208964192 (LWP 32105)] > [New Thread -1209230432 (LWP 32106)] > (no debugging symbols found) > (no debugging symbols found) > [New Thread -1209496672 (LWP 32107)] > (no debugging symbols found) > [New Thread -1209762912 (LWP 32108)] > (no debugging symbols found) > [New Thread -1210029152 (LWP 32109)] > (no debugging symbols found) > [New Thread -1210295392 (LWP 32110)] > (no debugging symbols found) > (no debugging symbols found) > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread -1208162640 (LWP 32098)] > 0x080639f8 in ast_channel_unregister () > (gdb) bt > #0 0x080639f8 in ast_channel_unregister () > #1 0x00a70e46 in key () from /usr/lib/asterisk/modules/chan_phone.so > #2 0x0805b5f5 in ast_unload_resource () > #3 0x0805bfcd in ast_unload_resource () > #4 0x0805c4ae in load_modules () > #5 0x080aebe9 in main () > > Is this of any help? Should I file a bug, if so where? Am I doing > something wrong maybe? You can get the debuginfo packages from here: http://people.atrpms.net/~athimm/asterisk/ It would be important to know whether you can get asterisk running under FC4. Is it possible to have an FC4 install and use the FC4 asterisk rpms? This is known to work well, so if oyu hit something there it should be something local. If you get no issues under FC4, then maybe it's something like gcc 4.1 that asterisk doesn't like. In the latter case it would be a bug report for asterisk to make the code gcc 4.1 compatible. -- Axel.Thimm at ATrpms.net
Attachment:
pgpFU2V8RlLWV.pgp
Description: PGP signature
-- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list