Hmm, Memcheck does very occasionally keel over like that, but the reason for it has never been established. Is it repeatable?
Were there any invalid reads/writes prior to this point, that might have trashed any Memcheck-specific data structures? Nick may well have something more constructive to add. J On Thursday 06 December 2007 01:11, Tom Hughes wrote: > I get an assertion in memcheck trying to valgrind a windows program > under wine. This is the current trunk code with a tweaked version of > the patch from > http://wiki.winehq.org/Wine_and_Valgrind applied. > > I'm just running "valgrind --trace-children=yes notepad" and I get: > > Memcheck: mc_main.c:957 (get_sec_vbits8): Assertion 'n' failed. > Memcheck: get_sec_vbits8: no node for address 0x6FA9EA0 (0x6FA9EAC) > > ==9850== at 0x38018ACD: report_and_quit (m_libcassert.c:140) > ==9850== by 0x8: ??? > ==9850== by 0x9: ??? > ==9850== by 0x9: ??? > ==9850== by 0x40000005: ??? > ==9850== by 0xFFFFFFFE: ??? > > Any ideas? > > Tom ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Valgrind-developers mailing list Valgrind-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-developers
