On Fri, Apr 15, 2005 at 09:16:43AM +0900, GOTO Masanori wrote: > At Wed, 13 Apr 2005 00:48:17 +0200, > Paolo wrote: > > well, SO5.2 is Debian-unrelated since there's no .deb for it, though it's > > related since it needs libc6. Whatever, it got broken, hope the > > Justification > > is ehm formally justified. > > > > I've been using SO 5.2 rather smoothly, till last update above, after which > > I get: > > > > ... > > (no debugging symbols found) > > (no debugging symbols found) > > [New Thread -1259529296 (LWP 6811)] > > > > Program received signal SIGSEGV, Segmentation fault. ... > but the invoked thread routine in SO 5.2 did not work. It might be SO > 5.2 specific problem.
maybe, but got similiar ssegv in other programs in Sarge (just can't remember as I didn't keep track) > > > apt-get updated a number of .deb as usual, though I think libc6 is likely > > to blame. Tried and verified on 2 similar (Sarge) systems. > > SO 5.2 still works fine on Slackware 10.1 (libc-2.3.4). > > Which libc6 version did you use? in Slackware? libc-2.3.4.so, that's it, what's come w/ distro, donnow the 'flavour'. As for Sarge, just what apt-get grabs for Sarge (now 'stable'). > If it's woody -> sarge problem, and if you have some knowledges to > create woody chroot environment with debootstrap, try to upgrade libc6 > only from woody to sarge on chroot. Then invoke SO 5.2. Otherwise, > we cannot track down because SO 5.2 is not part of Debian packages. couldn't do that (yet) - anyway did try a simpler thing, checked w/ kernel 2.4.x and 2.6.x: turns out it works w/ 2.4.x (2.4.31 now) but ssegv w/ 2.6.x (now 2.6.12.2 here). But, on a Slackware-based live-cd (slax), w/ 2.6.11.8 and libc-2.3.5 SO5.2 (same as above, load from hdd) works just fine. Also tried other kernel 2.4.x and 2.6.x I have ready and got no problems. Seems something Debian-specific - instead of teh chroot try as above, I may try to recompile libc for Sarge perhaps w/ different opts and/or w/out some patch (if any). Makes sense? what may I check recompiling Sarge's libc? -- paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
