|
From: <dom...@fr...> - 2006-03-16 21:24:11
|
Thanks for your reply. Agreed, I was using an old version of allegro. I was actually using the source package that comes with Ubuntu-5.10. I can successfully build the latest allegro-4.2 but allegro demo then does not work for me (init fails) for reasons I cannot fathom yet. Allegro-4.1.x at least works for me except when I try to use it with valgrind-3.1.1. Anyway, valgrind-3.1.1 should in theory work even with an old version of allegro. The valgrind assert() failure in particular should be a bug. I also thought about using 'configure --disable-asm' to build allegro but then build fails (link error) I will try to investigate it further later when I have more time. Cheers /Dominique Quoting Serge Semashko <se...@lx...>: > dom...@fr... wrote: > > First you are using very old allegro version, the most up to date > version is 4.2.0 > > Second, if you want to valgrind it, it is better to configure it as: > ./configure --disable-asm > > Depending on what you want to achieve, this information might be > enough :) [..snip...] > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > $ /usr/local/bin/valgrind --leak-check=3Dyes ~/allegro4.1-4.1.15/demo/d= emo > [...snip...] > vex x86->IR: unhandled instruction bytes: 0x6 0x8E 0x42 0x3C > [...snip...] > Shutting down Allegro due to signal #4 > not in syscall (0xB0044BBC - 0xB0044C11) > > valgrind: m_syswrap/syswrap-main.c:606 (vgPlain_client_syscall): Assert= ion > 'sci->status.what =3D=3D SsIdle' failed. > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D [...snip...] > $ /usr/local/bin/valgrind --version > valgrind-3.1.1 |