hi!
i've got a macro that i need for debugging code and i think it would be useful for b-t. it's called with-thread-name, that appends the given string to the thread's name and restores the old name in an unwind-protect.
it's useful when you have 10 nodes with 25 threads each and need to debug stuff like sbcl hanging in CLOSE on a socket.
if you like the idea i can move it into b-t and package up as a darcs patch.
On 26 Oct 2007, at 08:16, Attila Lendvai wrote:
hi!
i've got a macro that i need for debugging code and i think it would be useful for b-t. it's called with-thread-name, that appends the given string to the thread's name and restores the old name in an unwind-protect.
it's useful when you have 10 nodes with 25 threads each and need to debug stuff like sbcl hanging in CLOSE on a socket.
if you like the idea i can move it into b-t and package up as a darcs patch.
I had originally envisioned B-T as the most basic level of threading capability. Only provide enough so that implementation-specific code doesn't ever need to be called. However, there have been enough of these little helpers that don't really have anywhere else to go. It seems reasonable that they should be included in B-T somewhere. I think a patch that adds a new file that gets loaded after the implementation-specific file would be good.
bordeaux-threads-devel@common-lisp.net