Orxonox

Posted: **Fri Dec 29, 2006 2:30 pm**

Hi,

Maybe some here can enlighten me...

As both errors are glibc related, I rebuilt that package first, just to be sure.
From what I can tell, they happen at random, and it is not code related (same code, same build)

To my system: Gentoo 2006.1, with glibc-2.5, gcc-4.1.1, linux-2.6.19 (with some patches), Radeon M9600pro with flgrx drivers...

Code: Select all

=======================================================
= time: Fri Dec 29 13:18:24 2006
=======================================================
Program received signal SIGABRT, Aborted.
0xb7ffb410 in __kernel_vsyscall ()
(gdb)
#0  0xb7ffb410 in __kernel_vsyscall ()
#1  0x42b825ef in raise () from /lib/libc.so.6
#2  0x42c9cff4 in ?? () from /lib/libc.so.6
#3  0x00000000 in ?? ()
(gdb)
(gdb)

Code: Select all

=======================================================
= time: Fri Dec 29 15:20:13 2006
=======================================================
Program received signal SIGSEGV, Segmentation fault.
0x0825e862 in std::operator+<char, std::char_traits<char>, std::allocator<char> > ()
(gdb)
#0  0x0825e862 in std::operator+<char, std::char_traits<char>, std::allocator<char> > ()
#1  0x0816a8bc in std::operator+<char, std::char_traits<char>, std::allocator<char> > ()
#2  0x0816a6e5 in std::operator+<char, std::char_traits<char>, std::allocator<char> > ()
#3  0x081673eb in std::operator+<char, std::char_traits<char>, std::allocator<char> > ()
#4  0x08167054 in std::operator+<char, std::char_traits<char>, std::allocator<char> > ()
#5  0x0831dcdc in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char*> ()
#6  0x08192ad4 in std::operator+<char, std::char_traits<char>, std::allocator<char> > ()
#7  0x08194ac1 in std::operator+<char, std::char_traits<char>, std::allocator<char> > ()
#8  0x0819647c in std::operator+<char, std::char_traits<char>, std::allocator<char> > ()
#9  0xb577286b in __libc_start_main () from /lib/libc.so.6
(gdb)
(gdb)

cheers
nico

Posted: **Mon Jan 01, 2007 5:39 pm**

Can you try and use valgrind with this?

The first bug looks odd, but gdb sometimes gives these errors.

The second bug is from std::string (most probably) where a undefined or not '\0'-ended string is appended to another string.

Valgrind can tell you where this happens (hopefully):

On Gentoo do:

Code: Select all

emerge valgrind
valgrind --tool=memcheck ./src/orxonox &> orxonox.valgrind

And please post the output-file here (at least the section where Orxonox crashes)

Posted: **Wed Feb 07, 2007 9:06 pm**

Changed title to Obsolete:

I rebuild my entire system with glibc-2.4, and guess what, the error disappeared... It seems that error only occurred in glibc-2.5, which is what I expected.

Lets do some more important work such as preparing for the exams, or some bug squashing

cheers
nico

Posted: **Fri Apr 13, 2007 8:40 pm**

After some trial and error... (and glibc-2.5 gone stable) found the "error". Orxonox doesn't like an optimized glibc, and therefor fails. The USE=flags glibc-omitfp was the bugger.

cheers
nico

Orxonox

[OBSOLETE]libc.so.6 related errors

[OBSOLETE]libc.so.6 related errors