Opened 5 years ago
#19377 new enhancement
Add additional diagnostic information for the VERR_SUP_VP_THREAD_NOT_ALONE error
| Reported by: | rwreed | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 6.1.4 |
| Keywords: | VERR_SUP_VP_THREAD_NOT_ALONE | Cc: | |
| Guest type: | all | Host type: | Windows |
Description
Would it be possible to add additional information to the hardening log when this happens, to make it easier for users to identify the application that is causing the conflict?
For example, when VirtualBox detects an extra thread running that shouldn't be there, can you print a stacktrace to the hardening log that includes the DLL names for the code that is currently executing in that other thread?
Note:
See TracTickets
for help on using tickets.
