Colin Miller <[email protected]> writes: > tom fogal wrote: > > I'm seeing valgrind stack traces that point to errors from libraries > > which shouldn't be relevant to the given error messages. Here's an > > example: > > > > <snipped> > > > > Any idea what's going on, or how I might debug this further? > > Does your code call dlclose?
Well, yes, but only at shutdown time, at least for the file format reader in question. libGL is linked at compile time. > AIUI, valgrind only resolves address to functions when the app exits, > so if a .so is loaded into the space formerly occupied by another > .so, valgrind can get confused. Hrm? These errors come out while the program is running, not at the end of program execution. So I'm not sure this is (always) true, since the message is coming out long before the app exits. -tom ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
