THREADPOOL - Create Information Schema Table for Threadpool (MDEV-5019)

[MDEV-5046] THREADPOOL - information schema for windows Created: 2013-09-20  Updated: 2021-11-24  Resolved: 2021-11-24

Status: Closed
Project: MariaDB Server
Component/s: Platform Windows
Affects Version/s: None
Fix Version/s: N/A

Type: Technical task Priority: Minor
Reporter: roberto spadim Assignee: Vladislav Vaintroub
Resolution: Won't Do Votes: 0
Labels: None


 Description   

Different from UNIX, windows thread pool works with windows kernel, we should hack windows kernel to know about thread pool information

 Comments   
Comment by Vladislav Vaintroub [ 2021-11-24 ]

It is hard to hack the kernel, if even the documented debugger command to look at the threadpool internals does not work
I got that in windbg

0:011> !tp pool 0
 
Unable to read ${$ntdllsym}!_TP_POOL at 0x000001e356640d30: 3
 
0:011> !tp pool 0x000001e356640d30
 
Unable to read ${$ntdllsym}!_TP_POOL at 0x000001e356640d30: 3

The debug symbols for ntdll are loaded, but it seems that "public" only symbols are not enough,
and Microsoft does not offer good debugging experience with whatever is available from their symbol server.

People reported similar experience 10 years ago already - https://www.techsupportforum.com/threads/windbg-tp-command-problem.589531/

0:011> !lmi ntdll
 
Loaded Module Info: [ntdll] 
....
 
    Symbol Type: PDB      - Symbols loaded successfully from symbol server.
 
                 c:\symbols\ntdll.pdb\96EF4ED537402DAAA51D4A4212EA4B2C1\ntdll.pdb
 
    Load Report: public symbols , not source indexed 
                 c:\symbols\ntdll.pdb\96EF4ED537402DAAA51D4A4212EA4B2C1\ntdll.pdb

Comment by Vladislav Vaintroub [ 2021-11-24 ]

This does not really seems feasible. If we could at least debug those structs with a debugger , there could be a sign of hope. But currently, there is none.

Generated at Thu Feb 08 07:01:14 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.