On Friday 09 November 2007 12:54, Konstantin Serebryany wrote: > > I would be interested to know if that is useful. > It works and it is certainly useful!
Good. Thanks. > - as I see, the interceptors for pthread spin locks are not > implemented yet. Is that a principal limitation or just a matter of > time? Just a matter of time. > - If a spin lock/unlock routines are inlined by the compiler there is > no way for valgrind to intercept them, right? That's true; but it looks like they are not inlined: $ nm /lib/libpthread-2.5.so | grep spin 0000000000009e30 T pthread_spin_destroy 0000000000009e80 T pthread_spin_init 0000000000009e40 T pthread_spin_lock 0000000000009e60 T pthread_spin_trylock 0000000000009e80 T pthread_spin_unlock $ nm /lib64/libpthread-2.5.so | grep spin 000000000000ae50 T pthread_spin_destroy 000000000000aea0 T pthread_spin_init 000000000000ae60 T pthread_spin_lock 000000000000ae80 T pthread_spin_trylock 000000000000aea0 T pthread_spin_unlock so you should be able to easily make wrappers for them starting from the ones for pthread_mutex_*. > - How to show file names with full path in thrcheck's output? I think Nick and/or Josef know about this. I remember that a change was committed to trunk, which makes this work. When Thrcheck is merged to trunk (soon), then it will get that same functionality. J ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Valgrind-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-developers
