Re: [Svxlink-devel] svxlink doesn't start on mini itx pc
Brought to you by:
sm0svx
From: Kris C. (M. <k.c...@te...> - 2009-01-27 22:54:33
|
Hi Tobias, I have yesterday and now reinstalled gentoo on a other partition with a stage 3 tarbal from gentoo (stage3-x86-20090121.tar.bz2) the other installation was from www.funtoo.org (stage3-x86-2008.10.19.tar.bz2) the first time a had also a segfault , but just one's ? now it is running without problems and i have take the same configuration files for gentoo and other settings like my funtoo tarbal, for me not so funtoo , the say "using official Gentoo stable branch." but there may be a little difference. and it is the libc thats crash if i use the newly compiled binary svlink on the other booted funtoo glibc like to crash. yes i have noted before that i must compile it for a i486 processor just because cmov is not inplemented in the Cyrix processor and gcc like to use this asm-code when compiling for a i686 processor. for the callsign i have compiled and working the binary on my core 2 duo without problems an used these config files it is also changed in the /etc/svxlink.d/ModuleEchoLink.conf file if a have time, a take a look at the difference funtoo-gentoo , but for now on it back to gentoo's tarballs, i take a look to implement this on a CF-disk and remove de harddisk so whe have a silence (lowpower) system without moving parts Kris Coryn Op Sun, 25 Jan 2009 15:44:09 +0100 Tobias Blomberg <sm...@us...> Schreef: > Hi Kris, > > Do you still have this problem or is it resolved? > > Are you sure you have edited the correct configuration files? From > the printout it's obvious that /etc/svxlink.conf is what is loaded. > The EchoLink configuration should be > in /etc/svxlink.d/ModuleEchoLink.conf. Did you change the callsign > there? > > I know the mini-ITX hardware is a bit strage but if you compiled it > for i486 it should be OK. I know the mini-ITX I have is not i686 > compatible so applications crash if compiled for i686. > > 73's de SM0SVX / Tobias > > > On Monday 12 January 2009 22:57:26 Kris Coryn wrote: > > Hallo, > > > > I have svxlink working succesfully on my Core 2 Duo pc , but on the > > mini itx pc it doesnt start and have used the same configuration > > files from the other pc. > > > > when i start svxlink it say following : > > > > SvxLink v0.10.1 (Jan 4 2009) starting up... > > > > Using configuration file: /etc/svxlink.conf > > > > Starting logic: RepeaterLogic > > *** ERROR: Please set the EchoLink callsign > > (ModuleEchoLink/CALLSIGN) to a real callsign *** ERROR: > > Initialization failed for module ModuleEchoLink > > > > and if i look in the messages file i see also > > > > Jan 12 22:30:23 SvxLink svxlink[4681]: segfault at 20657461 ip > > b7bc86c8 sp bf92c214 error 4 in libc-2.6.1.so[b7b34000+121000] > > > > it like i have a segmentation fault but doesn't understand it > > because i have used the same calsign like my core 2 pc where it is > > ok > > > > what may be wrong here ? > > > > if it can help i have recompiled it with debug info and here some > > gdb debugging info and a attachment with a bt full debug log if > > usefull > > > > Starting program: /usr/bin/svxlink > > [Thread debugging using libthread_db enabled] > > [New Thread 0xb7a9c6d0 (LWP 4728)] > > > > Program received signal SIGSEGV, Segmentation fault. > > [Switching to Thread 0xb7a9c6d0 (LWP 4728)] > > free_dfa_content (dfa=0x20664920) at regcomp.c:571 > > 571 if (dfa->nodes) > > Current language: auto; currently c > > #0 free_dfa_content (dfa=0x20664920) at regcomp.c:571 > > #1 0xb7bf786f in __regfree (preg=0x940d798) at regcomp.c:622 > > #2 0xb78a4fd3 in ModuleEchoLink::moduleCleanup (this=0x940d6b0) at > > ModuleEchoLink.cpp:393 #3 0xb78a5fa1 in ~ModuleEchoLink > > (this=0x940d6b0) at ModuleEchoLink.cpp:163 #4 0x0806cb30 in > > Logic::loadModule (this=0x93e9f78, module_cfg_name=@0xbf95c720) at > > Logic.cpp:1010 #5 0x0806d80e in Logic::loadModules (this=0x93e9f78) > > at Logic.cpp:948 #6 0x0806f9de in Logic::initialize > > (this=0x93e9f78) at Logic.cpp:498 #7 0x08076199 in > > RepeaterLogic::initialize (this=0x93e9f78) at RepeaterLogic.cpp:150 > > #8 0x08061fc6 in main (argc=-1215575380, argv=0xb78bcae8) at > > svxlink.cpp:692 > > > > > > ldd svxlink > > > > linux-gate.so.1 => (0xb7f41000) > > libasynccpp.so.0.16 => /usr/lib/libasynccpp.so.0.16 > > (0xb7f2d000) libasyncaudio.so.0.16 => /usr/lib/libasyncaudio.so.0.16 > > (0xb7f03000) libdl.so.2 => /lib/libdl.so.2 (0xb7eff000) > > libpopt.so.0 => /usr/lib/libpopt.so.0 (0xb7ef7000) > > libspandsp.so.1 => /usr/lib/libspandsp.so.1 (0xb7e5f000) > > libgsm.so.1 => /usr/lib/libgsm.so.1 (0xb7e53000) > > libtcl8.4.so => /usr/lib/libtcl8.4.so (0xb7da5000) > > libstdc++.so.6 => > > /usr/lib/gcc/i486-pc-linux-gnu/4.1.2/libstdc++.so.6 (0xb7cbd000) > > libm.so.6 => /lib/libm.so.6 (0xb7c95000) > > libgcc_s.so.1 > > => /usr/lib/gcc/i486-pc-linux-gnu/4.1.2/libgcc_s.so.1 (0xb7c89000) > > libc.so.6 => /lib/libc.so.6 (0xb7b62000) libasynccore.so.0.16 > > => /usr/lib/libasynccore.so.0.16 (0xb7b48000) libsigc-1.2.so.5 > > => /usr/lib/libsigc-1.2.so.5 (0xb7b3d000) libpthread.so.0 > > => /lib/libpthread.so.0 (0xb7b26000) /lib/ld-linux.so.2 (0xb7f42000) > > libtiff.so.3 => /usr/lib/libtiff.so.3 (0xb7ad1000) > > libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0xb7ab0000) > > libz.so.1 => /lib/libz.so.1 (0xb7a9d000) > > > > > > my distro is a gentoo compiled for a i486 processor for the itx box > > and have emerge svxlink on both machines without problems if you > > want some specific information about something please ask me > > > > Kris Coryn > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > Svxlink-devel mailing list > Svx...@li... > https://lists.sourceforge.net/lists/listinfo/svxlink-devel > |