Serious problems with buggy glibc Sabayon PE 1.1

Anything that pertains to Portage

Moderator: Moderators

wolfden
Sharecropper
Posts: 9051
Joined: Sat Jan 14, 2006 0:55
Location: Midwest USA
Contact:

Re: Serious problems with buggy glibc Sabayon PE 1.1

Post by wolfden » Sat Dec 08, 2007 0:35

archwndas wrote:If I would have posted the errors you would be surprised and ask me again to post you the errors. Why? because that log file contains exactly the same message I have already posted:

These are the contents of the file /var/tmp/portage/sys-libs/glibc-2.6.1/temp/build.log:


* You still haven't deleted //etc/locales.build.
* Do so now after making sure //etc/locale.gen is kosher.
*
* ERROR: sys-libs/glibc-2.6.1 failed.
* Call stack:
* ebuild.sh, line 1717: Called dyn_setup
* ebuild.sh, line 768: Called qa_call 'pkg_setup'
* ebuild.sh, line 44: Called pkg_setup
* glibc-2.6.1.ebuild, line 204: Called die
* The specific snippet of code:
* die "lazy upgrader detected"
* The die message:
* lazy upgrader detected
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.6.1/temp/build.log'.
*
Well good than, no other errors and it's telling you what the issue is, so remove and all good.

archwndas
Advanced Hen
Posts: 207
Joined: Mon Jun 04, 2007 14:54

Re: Serious problems with buggy glibc Sabayon PE 1.1

Post by archwndas » Sat Dec 08, 2007 6:02

Hi Wolfden,
thank you very much for pointing out the way to do it. It worked. Unfortunately when I run my program under valgrind it still shows that there are major issues with the glibc library, see below. I installed SuSE 10.3 just for that reason. There are no errors with SuSE. So it is not a problem of my code but of the glibc library. The version of the glibc in SuSE is: 2.6.1-18.
I do not know what is happening. Any ideas? As you see something wrong happens in the ld library which ships with the glibc.

==18189== Invalid read of size 8
==18189== at 0x4013E34: (within /lib/ld-2.6.1.so)
==18189== by 0x4009CD5: (within /lib/ld-2.6.1.so)
==18189== by 0x4005E05: (within /lib/ld-2.6.1.so)
==18189== by 0x4007B2F: (within /lib/ld-2.6.1.so)
==18189== by 0x400AF5C: (within /lib/ld-2.6.1.so)
==18189== by 0x400C975: (within /lib/ld-2.6.1.so)
==18189== by 0x400B1FE: (within /lib/ld-2.6.1.so)
==18189== by 0x40109C6: (within /lib/ld-2.6.1.so)
==18189== by 0x400C975: (within /lib/ld-2.6.1.so)
==18189== by 0x40103A6: (within /lib/ld-2.6.1.so)
==18189== by 0x53E1CBF: (within /lib/libc-2.6.1.so)
==18189== by 0x400C975: (within /lib/ld-2.6.1.so)
==18189== Address 0x566E570 is 16 bytes inside a block of size 17 alloc'd
==18189== at 0x4A1FAE2: malloc (in /usr/lib/valgrind/amd64-linux/vgpreload_memcheck.so)
==18189== by 0x4008025: (within /lib/ld-2.6.1.so)
==18189== by 0x400AF5C: (within /lib/ld-2.6.1.so)
==18189== by 0x400C975: (within /lib/ld-2.6.1.so)
==18189== by 0x400B1FE: (within /lib/ld-2.6.1.so)
==18189== by 0x40109C6: (within /lib/ld-2.6.1.so)
==18189== by 0x400C975: (within /lib/ld-2.6.1.so)
==18189== by 0x40103A6: (within /lib/ld-2.6.1.so)
==18189== by 0x53E1CBF: (within /lib/libc-2.6.1.so)
==18189== by 0x400C975: (within /lib/ld-2.6.1.so)
==18189== by 0x53E1D74: (within /lib/libc-2.6.1.so)
==18189== by 0x53E1E47: __libc_dlopen_mode (in /lib/libc-2.6.1.so)

archwndas
Advanced Hen
Posts: 207
Joined: Mon Jun 04, 2007 14:54

Re: Serious problems with buggy glibc Sabayon PE 1.1

Post by archwndas » Sat Dec 15, 2007 0:44

Dear Wolfden,
I went to the glibc site to report the bug you see in my previous post. They say there that I have to make sure that this is not a bug of the distribution because several distributions modify the original glibc code. Could you let me know whether or not this is not a bug of the distribution itself? Try to compile the following piece of code in C++:

// C++ file main.cc
#include <iostream>
using std::cout

int main()
{
cout << "hello Wolfden\n";
return 0;
}

// end of file

Compile:
========
# > g++ main.cc -o run

Run valgrind:
===========
# > emerge valgrind
# > valgrind ./run

Let me know what happens please. The problem there may cause instabilities to several other applications.

Best,
Archwn.

DontPanic
Old Dear Hen
Posts: 742
Joined: Mon Jul 09, 2007 20:29
Location: Mobile, AL, USA

Re: Serious problems with buggy glibc Sabayon PE 1.1

Post by DontPanic » Sat Dec 15, 2007 17:05

Here's a data point for you:

I'm running under my Gentoo install (that has been built up in an attempt act like SabayonLinux) with sys-libs/glibc-2.6.1, dev-util/valgrind-3.2.3, and sys-devel/gcc-4.2.2 running an Athlon-XP 2600 cpu.

Here's my Valgrind output:

Code: Select all

# valgrind ./run
==26892== Memcheck, a memory error detector.
==26892== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==26892== Using LibVEX rev 1732, a library for dynamic binary translation.
==26892== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==26892== Using valgrind-3.2.3, a dynamic binary instrumentation framework.
==26892== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==26892== For more details, rerun with: -v
==26892==
hello Wolfden
==26892==
==26892== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 7 from 1)
==26892== malloc/free: in use at exit: 0 bytes in 0 blocks.
==26892== malloc/free: 0 allocs, 0 frees, 0 bytes allocated.
==26892== For counts of detected errors, rerun with: -v
==26892== All heap blocks were freed -- no leaks are possible.
I mad some minor variations from your instructions:
(1) using std::cout needed a ';' at the end of the line.
(2) I compiled with '-g' as per valgrinds quickstart.

I have SabayonLinux-3.4 miniCD edition running on another box, I'll see how it does there.
Gigabyte GA-P35-DS3L - Intel(R) Core(TM)2 Duo CPU [email protected] 2.66GHz
nVidia GeForce 7600 GS
2 GB RAM

DontPanic
Old Dear Hen
Posts: 742
Joined: Mon Jul 09, 2007 20:29
Location: Mobile, AL, USA

Re: Serious problems with buggy glibc Sabayon PE 1.1

Post by DontPanic » Sat Dec 15, 2007 17:47

I repeated the test on my stabilized and updated SabayonLinux-3.4 miniCD installation on an Intel(R) Pentium(R) 4 CPU 1.70GHz.

This box also has sys-devel/gcc-4.2.2, sys-libs/glibc-2.6.1, and dev-util/valgrind-3.2.3.

Looks good here too.

Code: Select all

==28730== Memcheck, a memory error detector.
==28730== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==28730== Using LibVEX rev 1732, a library for dynamic binary translation.
==28730== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==28730== Using valgrind-3.2.3, a dynamic binary instrumentation framework.
==28730== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==28730== For more details, rerun with: -v
==28730==
hello Wolfden
==28730==
==28730== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 7 from 1)
==28730== malloc/free: in use at exit: 0 bytes in 0 blocks.
==28730== malloc/free: 0 allocs, 0 frees, 0 bytes allocated.
==28730== For counts of detected errors, rerun with: -v
==28730== All heap blocks were freed -- no leaks are possible.
Gigabyte GA-P35-DS3L - Intel(R) Core(TM)2 Duo CPU [email protected] 2.66GHz
nVidia GeForce 7600 GS
2 GB RAM

archwndas
Advanced Hen
Posts: 207
Joined: Mon Jun 04, 2007 14:54

Re: Serious problems with buggy glibc Sabayon PE 1.1

Post by archwndas » Sun Dec 16, 2007 15:09

Thank you for the reply and the tests. But making sure that it works in other Sabayon versions doesn't mean that it should work in PE 1.1 x84 version. Could you try Sabayon Linux x86_64 PE 1.1? Just to make sure?

Maybe just booting from the live CD ...
Do you think I should install gcc-4.2.2?

Thanks in advance,
Archwn.

DontPanic
Old Dear Hen
Posts: 742
Joined: Mon Jul 09, 2007 20:29
Location: Mobile, AL, USA

Re: Serious problems with buggy glibc Sabayon PE 1.1

Post by DontPanic » Sun Dec 16, 2007 16:40

If you have gcc-4.1.2, I would expect that would work fine, but I haven't tested that assumption.

I'm sorry, but I don't have Sabayon PE installed. I don't think trying to run this from a Live-CD/DVD boot would allow a meaningful conclusion from a failure. I think you'd want an installed system that has been world-updated and stabilized.
Gigabyte GA-P35-DS3L - Intel(R) Core(TM)2 Duo CPU [email protected] 2.66GHz
nVidia GeForce 7600 GS
2 GB RAM

archwndas
Advanced Hen
Posts: 207
Joined: Mon Jun 04, 2007 14:54

Re: Serious problems with buggy glibc Sabayon PE 1.1

Post by archwndas » Mon Dec 17, 2007 17:35

And what is that system?

DontPanic
Old Dear Hen
Posts: 742
Joined: Mon Jul 09, 2007 20:29
Location: Mobile, AL, USA

Re: Serious problems with buggy glibc Sabayon PE 1.1

Post by DontPanic » Mon Dec 17, 2007 18:30

archwndas wrote:And what is that system?
Well, I guess I was speaking in reference to your question. So the system was SabayonLinux PE, meaning I would need SabayonLinux PE installed, USEFLAG properized, /etc/portage rationalized, world updated, revdep-rebuild'ed, etc., etc., in order to definitively answer the question.

But based on what I know of SabayonLinux and Gentoo, once you take just about any recent version of SabayonLinux, and world-update and stabilize that installation, I would expect the same results as I saw from my other Gentoo/SabayonLinux installations.

If I did see a problem, I'd be more suspicious of something I did in my update process rather than attributing it as a fundamental flaw in SabayonLinux glibc, especially since I'll typically rebuild glibc early and often in the updating process.
Gigabyte GA-P35-DS3L - Intel(R) Core(TM)2 Duo CPU [email protected] 2.66GHz
nVidia GeForce 7600 GS
2 GB RAM

DontPanic
Old Dear Hen
Posts: 742
Joined: Mon Jul 09, 2007 20:29
Location: Mobile, AL, USA

Re: Serious problems with buggy glibc Sabayon PE 1.1

Post by DontPanic » Tue Dec 18, 2007 0:36

I just noticed there was a valgrind upgrade available in portage. You may want to give that version a try.
Gigabyte GA-P35-DS3L - Intel(R) Core(TM)2 Duo CPU [email protected] 2.66GHz
nVidia GeForce 7600 GS
2 GB RAM

Post Reply