I compiled kvirc without problems, but it segfaults on startup. $ kvirc Segmentation fault $ gcc -v Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.1.1/specs Configured with: /usr/tmp/portage/gcc-3.1.1-r1/work/gcc-3.1.1/configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --target=i686-pc-linux-gnu --with-system-zlib --enable-languages=c,c++,ada,f77,objc,java --enable-threads=posix --enable-long-long --disable-checking --enable-cstdio=stdio --enable-clocale=generic --enable-version-specific-runtime-libs --with-gxx-include-dir=/usr/include/g++-v31 --with-local-prefix=/usr/local --enable-shared --enable-nls --without-included-gettext Thread model: posix gcc version 3.1.1 I have a dual ahtlon-mp box with the latest gentoo kernel. compilerflags CHOST="i686-pc-linux-gnu" CFLAGS="-march=athlon-mp -O3 -pipe" CXXFLAGS="-march=athlon-mp -O3 -pipe"
I just compiled kvirc-3.0.0-beta1 from the sources of the website. This compile seems to work.
OK, so let's go over the differences of compiling it by hand and from the ebuild. Try making the by-hand compile as similar to the ebuild one is possible, until you get the segfault. Then remove these changes one by one until it disappears. Things to try: export CFLAGS, CXXFLAGS as per your make.conf; export KDEDIR=/usr/kde/3 and install into /usr (--prefix=/usr); look at the configure options in the ebuild and try enabling them one by one (things like --with-ix86-asm --with-{ipv6,kde,arts,esd}-support --with-aa-fonts).
It's compiling and running on two of my boxes (athlon, pII), segfault on an other (athlon). The two athlons have the same compiler options.
psk: please try what I said about finding the cause then? Or at least compile qt, kdelibs etc and kvirc with --enable-debug (export DEBUG=1), get a nice trace and send it upstream to bugs.kvirc.org :-)
Is this still relevant? Please respond!
It'sworking for me now, on all my boxes.(not like the cvs snapshot that I've tested.)
Niels? Is this still relevant?
No, thanks
psk, you're Niels? ;-)
Who knows... Hehe. Sorry, I havn't seen that you was talking to him.
Im sorry i havent responded in a while. This is no longer relevant. I can compile kvirc now. Thanks!
Oops.. And most important.. run it :) Sorry.
Well, let me jump in here b4 this is closed. Comes up with boxes instead of glyphs in the UI (first time running it, I assume some kind of config dialog is happening). Try clicking on some mystery buttons, get segfault with this traceback (Note this was built with gcc 2.95.3): (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)... (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 1024 (LWP 26486)] (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)...(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)...(no debugging symbols found)... 0x4109a2f9 in wait4 () from /lib/libc.so.6 #0 0x4109a2f9 in wait4 () from /lib/libc.so.6 #1 0x4111bba0 in __check_rhosts_file () from /lib/libc.so.6 #2 0x40e438d6 in waitpid () from /lib/libpthread.so.0 #3 0x405df6bc in KCrash::defaultCrashHandler () from /usr/kde/3/lib/libkdecore.so.4 #4 0x40e416e4 in pthread_sighandler () from /lib/libpthread.so.0 #5 0x4101d998 in sigaction () from /lib/libc.so.6 #6 0x40f64420 in XftDrawDestroy () from /usr/X11R6/lib/libXft.so.1 #7 0x408d9189 in QPixmap::deref () from /usr/qt/3/./lib/libqt-mt.so.3 #8 0x409749e4 in QPixmap::~QPixmap () from /usr/qt/3/./lib/libqt-mt.so.3 #9 0x408d910b in QPixmap::deref () from /usr/qt/3/./lib/libqt-mt.so.3 #10 0x409749e4 in QPixmap::~QPixmap () from /usr/qt/3/./lib/libqt-mt.so.3 #11 0x40057c69 in KviImageLibrary::unloadLibrary () from /usr/lib/libkvilib.so.3 #12 0x40057c0b in KviImageLibrary::~KviImageLibrary () from /usr/lib/libkvilib.so.3 #13 0x080b2b63 in KviIconManager::KviIconManager () #14 0x080a679f in KviApp::setup () #15 0x080b9b9d in main () #16 0x4100c3ce in __libc_start_main () from /lib/libc.so.6 Also, stdout shows: WARNING: KDE detected X Error: 174 174 Major opcode: 152 over and over, presumably one per rectangle character...
Carl: do you have kde support enabled (kde use flag) or is kvirc just using qt? What versions of qt and kdelibs? What CFLAGS? Are there any other font-related problems on your system? A pity kvirc hasn't had a new release for so long now. (And remember this is just a beta release we're using; we have it because it's the first for kde3.) The first time you run kvirc, a config wizard comes up (if you have no previous config, which would be under ~/kvirc-3.0.0-beta1). You can press Escape to abort it, see if that works (ie brings up the main kvirc window wihout crashing). I'm attaching my kvirc config file (one of many, this is the main one), try putting it in ~/kvirc-3.0.0-beta1/config directory, filename main.kvc. It forces all fonts used to Verdana, change it to something else if you don't like it (note there are multiple font entries in the file). Run kvirc and see if it works, font-wise and in general.
Created attachment 6165 [details] My main.kvc - kvirc main config file
adding carl so he can answer the questions ;) Carl: please take a look at comment #14 & #15. thanks.
Oh, hey, sorry to be asleep at the wheel here! :) USE flags: USE="gnome bonobo -ipv6 mozilla mozxmlterm mozinterfaceinfo mozp3p moznoirc innodb -berkdb gpm 3dfx voodoo3 gphoto2 gpm X xmms truetype freetype scanner cups" I assume kde and qt are picked up as default flags from /etc/make.profile/make.defaults kdelib version = 3.0.4-r1 qt version = 3.1.0-r1 CHOST="i686-pc-linux-gnu" CFLAGS="-march=i686 -O3 -pipe" Still crashes just hitting ESC (after removing ~/kvirc-3.0.0-beta1/) Same using the attached main.kvc in ~/kvirc-3.0.0-beta1/config Hope this helps!
Well, the next thing to try is the latest kvirc cvs, since beta1 really is quite old. I'll try to make a reasonably stable snapshot - last time I checked it didn't even compile. (Masked, of course.) You could also try compiiling it without kde support (i.e. qt-only) and seeing if that helps.
I've tryed directly CVS version, numerous times since I've posted this bug. I do not compile at all, in fact, the autosgen.sh script stop just after few lines. I've just made an rsync and I'm on the way to try your snapshot.
OooOoOps, I've read too quickly. I'll wait that you release your snapshot before testing it. (the last one don't work) I can beta test if that can help you...
Our mirroring setup is currently borken, I waited for it to be fixed, which caused this delay. I've ended up placing it in my homedir's public_html on chiba. I've committed a masked ebuild that fetches it from there, please test it. It's a cvs snapshot that compiles and runs very nicely here.
It compile and seems to work perfectly. Excellent job, thx for all !!!
Actually... I've found some problems with the ebuild - kde support doesn't compile well (qt-only is what works), etc... So I've decided not to unmask it. It will stay masked for those who have this problem. I don't have time to explore this further atm :-(
I've committed a beta2 ebuild (unmasked). As I understand it the problems reported here are now gone (reopen this bug if that isn't so).
