Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If you create a basic VCL application and execute it, there are a few threads running. What are each of the threads for and can they be named to make it easier to debug multi-threaded applications?
I try to name all my child threads and it would be useful in debugging to have a clear idea of what each child thread is doing when viewing the Thread Status debug window. (And if one isn’t named it would be a hint to track it down and get it named.)
A plain vanilla 32 bit VCL app in XE2, running on 64 bit Windows 7 has 3 threads. The main thread and two extras. The two extra threads are created in
TApplication.CreateHandleby a call toWTSRegisterSessionNotification. If you want to name them then you can enumerate the threads in the process and callNameThreadForDebugging.In my experience, it’s very hard to keep track of all the threads in your app. As soon as your app becomes moderately complex then there are liable to be plenty of threads coming and going. I personally view the ones that I have not named as being somebody else’s responsibility!