Global variable "_pgmptr" uninitialized in mingwrt-3.21 and later

Keith Marshall <[email protected]> Tue, 1 Sep 2020 21:48:30 +0100

Newsgroups	gmane.comp.gnu.mingw.user
Organization	MinGW.org Project
Message-ID	<[email protected]>

This is primarily a heads-up: I discovered it while testing my strategy
for invocation of GDB, such that it will use python-2.7, if available,
but does not require it.

I alluded to the issue in list posting:
https://osdn.net/projects/mingw/lists/archive/users/2020-September/000625.html

According to Microsoft's documentation for GetModuleFileName():
https://docs.microsoft.com/en-us/windows/win32/api/libloaderapi/nf-libloaderapi-getmodulefilenamea
> The global variable _pgmptr is automatically initialized to the
> full path of the executable file, and can be used to retrieve the
> full path name of an executable file.
I guess that not many MinGW users rely on this, because mingwrt hasn't
performed this initialization, since the release of mingwrt-3.21, back
in December 2014.

I've filed a bug report:
https://osdn.net/projects/mingw/ticket/40696

-- 
Regards,
Keith.

Public key available from keys.gnupg.net
Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F

_______________________________________________
MinGW-Users mailing list
[email protected]

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.  Disregard for the list etiquette may cause your account to be moderated.

_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.osdn.me/mailman/listinfo/mingw-users
Also: mailto:[email protected]?subject=unsubscribe

signature.asc (application/pgp-signature, 833 B)