Root > Reference > All Functions > AquireThreadData

Function AquireThreadData

Previous pageReturn to chapter overviewNext page   

Returns thread information (any thread).







Code (Delphi)

function AquireThreadData(

const AThreadID: Cardinal;

const AForce: Boolean = False

): TEurekaThreadData;



AThreadID [in]

TID (Thread ID) of a thread to get information.


AForce [in, optional]

True: return dummy object for empty result, false (default): return nil for empty result.


Return value

Information about the AThreadID thread. You have to destroy the returned object. This value could be nil for rare cases (such as calling this function before/after EThreadsManager's initialization/finalization), or if AThreadID does not identify a valid running thread. The return value is always non-nil if AForce argument is True.



Use this function to get information about any running thread.


You have to release the returned object. A new return value object is created for each function's call.


There is no need to use locking - because informational object for the thread will be individual for each function's call. Any change for dynamic properties (such as Name, LastException, LastHTMLPage) will be ignored. Use ThreadData function to modify thread's dynamic properties.


This function can return information about any running thread.



This function returns information only about running threads. Return value will be empty if AThreadID identifies already terminated thread.


See also

Send feedback... Build date: 2023-05-05
Last edited: 2023-05-05
The documentation team uses the feedback submitted to improve the EurekaLog documentation. We do not use your e-mail address for any other purpose. We will remove your e-mail address from our system after the issue you are reporting has been resolved. While we are working to resolve this issue, we may send you an e-mail message to request more information about your feedback. After the issues have been addressed, we may send you an email message to let you know that your feedback has been addressed.

Permanent link to this article: