The problem was the .so library... Thanks anyway :)
On Tue, Dec 23, 2008 at 5:11 PM, Wayne Arnold <[email protected]> wrote: > If you need more info on Maya itself and Valgrind, I may be able to help > > I know the latest Nvidia drivers 180.xx don't mix with Maya and valgrind, > reported to Nvidia, I haven't had a resolution yet. > As well the newer Intel compilers 10.1.x/11.0 can have problems with debug > symbol generation, with -O3 -g compile options > > > > -----Original Message----- > From: Michele Gregori [mailto:[email protected]] > Sent: Tuesday, December 23, 2008 10:44 AM > To: [email protected] > Subject: Re: [Valgrind-users] valgrind and maya > > I've sent the file... Hope this help > > > On Tue, Dec 23, 2008 at 1:45 PM, Julian Seward <[email protected]> wrote: >> >> This is a bug in Valgrind. >> >> > valgrind: m_debuginfo/debuginfo.c:527 (check_CFSI_related_invariants): >> > Assertion 'di->cfsi_minavma >= di->rx_map_avma' failed. >> >> This happened when Valgrind was reading debugging information from a >> shared object (.so), yes? You can check by rerunning with -v. >> >> If so, can you compress the .so with bzip2 and send it to me in private >> email? >> >> J >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Valgrind-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/valgrind-users > > ------------------------------------------------------------------------------ > _______________________________________________ > Valgrind-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/valgrind-users > ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
