lockups & Seg faults [Re: libsigc++ problems in Yoper]

From: Mike Hearn <mike@...519...> Re: libsigc++ problems in Yoper [Re: Please Help: Yoper linux packaging/compiling problems] 2004-08-22 09:06
"Could not find "libsigc C++ callback library""
That"s odd. It should have downloaded it and
installed it for you.
Bugs, bugs, everywhere ....
It did d/l some other packages before libsigc.
- There is no such package for Yoper yet
- I config/make/make install libsigc-1.2.so5 (I
think
Check that /usr/local/lib is actually in your linker
path and
that you reran ldconfig as root.
OK, that worked. New tests:
1) ./inkscape-0.40cvs.package installed everything fine inkscape -V said "Aug 21 2004" ran inkscape & got "Segmentation fault" & wouldn't run
2) package remove inkscape ./inkscape-0.39.package installed everything fine ran inkscape in shell & inkscape window opened fine (though I did notice window resizing was slow on my AthlonXP 2200) drew a square shape, computer locked up (I could move mouse, but not click, & [Enter] wouldn't work) shell said "Emergency save activated! completed..." had to do a hardware reboot (couldn't reboot in linux) (BTW: I have the exact same lockup problem with .39 in Win98se & Mandrake Cooker on the same computer. But Debian unstable seemed to work fine.)
3) package remove inkscape ./inkscape-0.40cvs.package installed everything fine, though re-installed libsigc again inkscape -V said "Aug 21 2004" ran inkscape & got "Segmentation fault" & wouldn't run
cheers
===== high-speed downtempo radio: http://live365.com/stations/infuzon
_______________________________ Do you Yahoo!? Express yourself with Y! Messenger! Free. Download now. http://messenger.yahoo.com

On Sun, 2004-08-22 at 14:06, tom b wrote:
ran inkscape in shell & inkscape window opened fine (though I did notice window resizing was slow on my AthlonXP 2200) drew a square shape, computer locked up (I could move mouse, but not click, & [Enter] wouldn't work) shell said "Emergency save activated! completed..." had to do a hardware reboot (couldn't reboot in linux) (BTW: I have the exact same lockup problem with .39 in Win98se & Mandrake Cooker on the same computer. But Debian unstable seemed to work fine.)
Hmm, could you switch to another virtual console, log in, and kill Inkscape? I suspect it had a mouse and keyboard grab.
If killing Inkscape didn't work, try killing the X server.
If the machine is actually locked to the point where you can't even do that, you have a hardware, kernel, or X bug, not (just) an Inkscape bug.
-mental

On Sun, 22 Aug 2004 11:06:07 -0700, tom b wrote:
ran inkscape & got "Segmentation fault" & wouldn't run
I'm going to investigate this now. It happens for me as well now *but* on Fedora Core 1 the very same package runs just fine. Judging from the backtrace of the crash something is trashing the stack, and given that the exact same binary works on older distros but NOT on newer like FC2, Debian Unstable and now I guess Yoper it looks like some library broke the ABI but didn't bump the soname.
At least, this is my current theory. I'll try tracking down what changed. But it would not surprise me in the slightest if this sort of ABI breakage was more common than expected: the practice of rebuilding packages continuously for every distro revision is almost certainly hiding some kinds of ABI breakage.
thanks -mike (who is still curious why it didn't install sigc++ first, but never used yoper so maybe it's different in some subtle way)
participants (3)
-
MenTaLguY
-
Mike Hearn
-
tom b