We all know that gdbserver's thread support is in the toilet, but I'm wondering what the gurus do when it comes to trying to debug threaded programs remotely.
The best idea I had on the matter was to have each thread call a dummy function, stupid_gdbserver_hack(), which I could break on as gdbserver became aware of each thread, but that didn't work at all. :-) So far I've been pretty lucky and not needed to worry about this too much, but I'm curious as to what others can and have done in the past? -A. _______________________________________________ uClinux-dev mailing list [email protected] http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by [email protected] To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
