dbghelp: Don't include global & static variables from S_LOCAL* records.
commit87e2b007744f8bafdea63df21a74ffc24b392912
authorEric Pouech <eric.pouech@gmail.com>
Tue, 12 Jul 2022 07:28:57 +0000 (12 09:28 +0200)
committerAlexandre Julliard <julliard@winehq.org>
Tue, 12 Jul 2022 20:51:29 +0000 (12 22:51 +0200)
tree9d1f58b8a18b9f7b73dced3e87b2eb884932aa56
parent437e73883bd73eb219ba722b2fbba6398fc75343
dbghelp: Don't include global & static variables from S_LOCAL* records.

PDB supports description of a global or static variable:
- accessed from a register
- stored as a local variable record inside a function

This likely describes access to a global/static variable where
intermediate computation is kept in a register.

We cannot store this kind of entries in local variable lists
(builtin dbghelp and winedbg are not prepared to handle a global variable)

Note: the global or static Codeview data record is still present (with a
relocatable address), so the variable should still be available from global
access (but could be not up-to-date if temporarly stored in a register).

Signed-off-by: Eric Pouech <eric.pouech@gmail.com>
dlls/dbghelp/msc.c