[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: libvorbis - replace
Greg Troxel wrote:
Riccardo Mottola <riccardo.mottola%libero.it@localhost> writes:
"cd /var/db/pkg; ls -lt */+CONTENTS". Look at all the things
windowmaker depends on and see if you an spot anything that was built
out of order. Probably all is ok if pkg_rr -uv doesn't do anything.
I suppose I need to chececk only the stuff that lives in /usr/pkg/lib,
right? that's surprisingly little stuff.
-lWINGs.2 => /usr/pkg/lib/libWINGs.so.2
-lWUtil.3 => /usr/pkg/lib/libWUtil.so.3
-lwraster.3 => /usr/pkg/lib/libwraster.so.3
-ltiff.5 => /usr/pkg/lib/libtiff.so.5
-ljbig.2 => /usr/pkg/lib/libjbig.so.2
-ljpeg.9 => /usr/pkg/lib/libjpeg.so.9
-lpng16.16 => /usr/pkg/lib/libpng16.so.16
-lgif.7 => /usr/pkg/lib/libgif.so.7
I suppose the 3 first libraries are internal to wmaker and not
separate, right? I couldn't find specific packages.
Hard to tell without grepping for them in */+CONTENTS.
The first 3, WINGS, WUtil, wraster are noth tere, for the other I find:
-rw-r--r-- 1 root wheel 20009 Jun 11 09:59 tiff-4.0.3nb6/+CONTENTS
-rw-r--r-- 1 root wheel 1539 Jun 11 09:47 jbigkit-2.1/+CONTENTS
-rw-r--r-- 1 root wheel 2203 Feb 9 01:15 jpeg-9anb1/+CONTENTS
-rw-r--r-- 1 root wheel 1473 Jun 6 00:24 png-1.6.11/+CONTENTS
-rw-r--r-- 1 root wheel 615 Jun 5 01:55 giflib-5.1.0/+CONTENTS
(I rebuilt tiff and jbig kit today, just to be sure, they were of a
previous build run, same version though).
wmaker itself is:
-rw-r--r-- 1 root wheel 33608 Jun 6 21:15
I then grepped inside it
we can say the answer is yes, right?
run windowmaker under gdb
I think this is what you'll have to do.
It gives a quite unreadable gdb. Wmaker forks, so just "gdb wmaker" is
not of help, but it will leave a core file, wif I analyize it
post-morten, I see:
Core was generated by `wmaker'.
Program terminated with signal 11, Segmentation fault.
#0 0x08097e34 in ?? ()
#0 0x08097e34 in ?? ()
#1 0x0806eab0 in ?? ()
#2 0xbbbad534 in WMHandleEvent () from /usr/pkg/lib/libWINGs.so.2
#3 0x0808d28b in ?? ()
#4 0x080a4af3 in ?? ()
#5 0x0804fedd in ?? ()
#6 0x0804fdb8 in ?? ()
Possibly, I doubt that faithful windowmaker broke down now... something
changed under its feet.
It's seeming more likely that there is a problem than that you have a
broken environment. It would be perhaps helpful to precisely describe
how to reproduce the problem and exactly what the problem is.
What other information may I provide? Does netbsd have a tool similar to
revdep rebuild on gentoo that checks for broken symbols in all
execs/libraries? However I think here we can restrict to windowmaker.
Main Index |
Thread Index |