[0.4.14][DBGHELP] Addendum to last commit CORE-17073 (#3257)
authorJoachim Henze <Joachim.Henze@reactos.org>
Sat, 10 Jul 2021 10:54:32 +0000 (12:54 +0200)
committerJoachim Henze <Joachim.Henze@reactos.org>
Sat, 10 Jul 2021 10:54:32 +0000 (12:54 +0200)
commit651a0115480848b51ad0c20c1e0226c6bd8925f0
tree4097979493398b0a7a4dc3f488b57fa8cf12e44a
parentd3e301e28b16a2a2d9f7617a6e431d57bcc1879d
[0.4.14][DBGHELP] Addendum to last commit CORE-17073 (#3257)

I do recommend to change in function SymSetSearchPath: the line
WCHAR* sp;
to
WCHAR* sp = NULL;

to avoid the following compiler warning, that I got only on carrier-releaser interestingly,

../dll/win32/dbghelp/dbghelp.c: In function 'SymSetSearchPath':
../dll/win32/dbghelp/dbghelp.c:244:9: error: 'sp' may be used uninitialized in this function [-Werror=uninitialized]
cc1: all warnings being treated as errors

but I did not get that error on compilation when building this locally on "GCC4.7.2 RosBE2.1.6"
or "GCC8.4.0 RosBE2.21", or "VS2010", or with the buildbits/testbots. Weird!
I have no clue, why carrier releaser does behave different here at all upon compilation!
dll/win32/dbghelp/dbghelp.c