Glenn Smith

Here's a few more from notepad.exe: ``` Undecoration of :- "?dismissButtonImageList@@3V?$unique_any_t@V?$unique_storage@U?$resource_policy@PEAU_IMAGELIST@@P6AHPEAU1@@Z$1?ImageList_Destroy@@YAH0@ZU?$integral_constant@_K$0A@@wistd@@PEAU1@PEAU1@$0A@$$T@details@wil@@@details@wil@@@wil@@A" is :- "class wil::unique_any_t dismissButtonImageList" Undecoration of :- "?messageFont@@3V?$unique_any_t@V?$unique_storage@U?$resource_policy@PEAUHFONT__@@P6AHPEAX@Z$1?DeleteObject@@YAH0@ZU?$integral_constant@_K$0A@@wistd@@PEAU1@PEAU1@$0A@$$T@details@wil@@@details@wil@@@wil@@A" is :- "class wil::unique_any_t messageFont" Undecoration of :- "?messageString@@3V?$unique_any_t@V?$unique_storage@U?$resource_policy@PEAGP6AXPEAX@Z$1?CoTaskMemFree@@YAX0@ZU?$integral_constant@_K$0A@@wistd@@PEAGPEAG$0A@$$T@details@wil@@@details@wil@@@wil@@A" is...

Addressed in 3.5.4468 though not exactly a _demangler_ problem: some PDB symbol names start with a DEL (`\x7f`) character. Now these characters are just stripped off.

Nope, I have no clue why they do that. This only happens on non-mangled names though. It looks like the various null thunk data symbols stored around the module imports...

Here's another one. It looks like the backref is getting eaten somewhere and it cannot reference it: ``` Undecoration of :- "??4?$Resource@VTSShape@@@@QAEAAV0@ABV0@@Z" is :- "public: class Resource & __thiscall Resource::operator=(class...

Now included, even if nobody here asked for it: bare names of the construction `.?AV` or `.?AU`. I'm not sure what the difference between AV and AU is, so they're...

As of 3.6.4615, a bug in template back-references has been fixed. This has fixed the following: ``` ??_G?$_Func_impl@P6A_NAEBW4agent_status@Concurrency@@@ZV?$allocator@H@std@@_NAEBW412@@std@@QEAAPEAXI@Z MSVC public: void * __ptr64 __cdecl std::_Func_impl::`scalar deleting destructor'(unsigned int) __ptr64 LLVM...

3.6.4629 added slightly more stuff for type info names since I found the code in LLVM that parses them and was able to expand our parser to cover the cases....

Some basic names with the construction `$1?Name@@Type@@` are now handled, looks to be a template param with a &reference to an existing symbol. Coverage isn't super great because there's an...

> It also says the first field `OutputBufferLength` is at offset `0x8`, when it should be `0x4`. Looking at the header I have (wdm.h from 10.0.19041.0), I think those offsets...

My guess is a lot of the confusion comes from the lack of union type support (see #1013), which is a known limitation that, while we have plans to address...