Aw: BUG #18312: libpq: PQsetdbLogin() not thread-safe
Christian Maurer <c.maurer@gmx.at>
From: Christian Maurer <c.maurer@gmx.at>
To: pgsql-bugs@lists.postgresql.org
Date: 2024-02-02T10:10:54Z
Lists: pgsql-bugs
Attachments
- (unnamed) (text/html)
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi</div> <div> </div> <div>I managed to capture a stack trace for the crash via WinDbg:</div> <div> </div> <div>Frame Index Call Site Child-SP Return Address<br/> [0x0] ntdll!NtTerminateProcess+0x14 0x18aa9fdf88 0x7fffce3cda98<br/> [0x1] ntdll!RtlExitUserProcess+0xb8 0x18aa9fdf90 0x7fffcd99e82b<br/> [0x2] KERNEL32!ExitProcessImplementation+0xb 0x18aa9fdfc0 0x7fffcd42a155<br/> [0x3] msvcrt!_crtExitProcess+0x15 0x18aa9fdff0 0x7fffcd42a7c5<br/> [0x4] msvcrt!doexit+0x171 0x18aa9fe020 0x7fffcd41f26d<br/> [0x5] msvcrt!abort+0x8d 0x18aa9fe090 0x68281886<br/> [0x6] libintl_9!libintl_bindtextdomain+0x56 0x18aa9fe640 0x7fff7dcd2e93<br/> [0x7] LIBPQ!PQenv2encoding+0x1193 0x18aa9fe670 0x7fff7dcd2c9e<br/> [0x8] LIBPQ!PQenv2encoding+0xf9e 0x18aa9fe6a0 0x7fff7dcc9263<br/> [0x9] LIBPQ!PQpingParams+0x2ea3 0x18aa9fe6d0 0x7fff7dcc3dcd<br/> [0xa] LIBPQ!PQconnectPoll+0x90d 0x18aa9feb50 0x7fff7dcc6a1c<br/> [0xb] LIBPQ!PQpingParams+0x65c 0x18aa9ff5c0 0x7fff7dcc50eb<br/> [0xc] LIBPQ!PQsetdbLogin+0x19b 0x18aa9ff5f0 0x7ff774798078<br/> [0xd] _HelloWorld!test+0x98 0x18aa9ff620 0x7ff774796f17</div> <div> </div> <div>It seems to me, that it is related to BUG #17299</div> <div> </div> <div>Regards,</div> <div>Christian Maurer<br/> <br/> <br/> </div></div></body></html>
Commits
-
Avoid concurrent calls to bindtextdomain().
- a584d03ced5f 17.0 landed
- 9fb1396a96bd 12.19 landed
- 8ead39e3895e 14.12 landed
- 8c5da20db298 13.15 landed
- 806f98951511 15.7 landed
- 52afe563206e 16.3 landed