DAC/DBI/SOS Treatment of Dead and Report as Dead threads is inconsistent.

[sdmaclea]

From a conversation with @clguiman

I started debugging the original ttd trace and at position 6307D:551 (DacDbiInterfaceImpl::EnumerateThreads) pThread is the first thread (
dx pThread->m_OSThreadId

)

and pThread->m_State ==TS_LegalToJoin | TS_Background| TS_ReportDead | TS_FullyInitialized | TS_Finalized

The thread is considered dead and shouldn't be a managed thread so I suspect dotnet-dump shouldn't show it

    Thread::GetSnapshotState() marks all threads with TS_ReportDead with TS_Dead

We may need to look through how these flags affect DAC/DBI/SOS.

I am not sure how much of a concern this is.

/cc @clguiman @mikem8361

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

---

Issue meta data

Issue content:
	From a conversation with @clguiman I started debugging the original ttd trace and at position 6307D:551 (DacDbiInterfaceImpl::EnumerateThreads) pThread is the first thread ( dx pThread->m_OSThreadId ) and pThread->m_State ==TS_LegalToJoin | TS_Background| TS_ReportDead | TS_FullyInitialized | TS_Finalized The thread is considered dead and shouldn't be a managed thread so I suspect dotnet-dump shouldn't show it Thread::GetSnapshotState() marks all threads with TS_ReportDead with TS_Dead We may need to look through how these flags affect DAC/DBI/SOS. I am not sure how much of a concern this is. /cc @clguiman @mikem8361 </td>
Issue author:		sdmaclea
Assignees:	-
Labels:	`area-Diagnostics-coreclr` </td>
Milestone:	-

[dotnet-policy-service]

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

[dotnet-policy-service]

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.