| From: | Christian Maurer <c(dot)maurer(at)gmx(dot)at> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Aw: BUG #18312: libpq: PQsetdbLogin() not thread-safe |
| Date: | 2024-02-02 10:21:46 |
| Message-ID: | trinity-bf4e8296-ed0b-48cd-8a8c-86135d8dd5d9-1706869306101@3c-app-gmx-bap04 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi
(Again. Sorry for the html-formatting in my previous mail.)
I managed to capture a stack trace for the crash via WinDbg:
Frame Index Call Site Child-SP Return Address
[0x0] ntdll!NtTerminateProcess+0x14 0x18aa9fdf88 0x7fffce3cda98
[0x1] ntdll!RtlExitUserProcess+0xb8 0x18aa9fdf90 0x7fffcd99e82b
[0x2] KERNEL32!ExitProcessImplementation+0xb 0x18aa9fdfc0 0x7fffcd42a155
[0x3] msvcrt!_crtExitProcess+0x15 0x18aa9fdff0 0x7fffcd42a7c5
[0x4] msvcrt!doexit+0x171 0x18aa9fe020 0x7fffcd41f26d
[0x5] msvcrt!abort+0x8d 0x18aa9fe090 0x68281886
[0x6] libintl_9!libintl_bindtextdomain+0x56 0x18aa9fe640 0x7fff7dcd2e93
[0x7] LIBPQ!PQenv2encoding+0x1193 0x18aa9fe670 0x7fff7dcd2c9e
[0x8] LIBPQ!PQenv2encoding+0xf9e 0x18aa9fe6a0 0x7fff7dcc9263
[0x9] LIBPQ!PQpingParams+0x2ea3 0x18aa9fe6d0 0x7fff7dcc3dcd
[0xa] LIBPQ!PQconnectPoll+0x90d 0x18aa9feb50 0x7fff7dcc6a1c
[0xb] LIBPQ!PQpingParams+0x65c 0x18aa9ff5c0 0x7fff7dcc50eb
[0xc] LIBPQ!PQsetdbLogin+0x19b 0x18aa9ff5f0 0x7ff774798078
[0xd] _HelloWorld!test+0x98 0x18aa9ff620 0x7ff774796f17
It seems to me, that it is related to BUG #17299
Regards,
Christian Maurer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2024-02-02 13:05:56 | BUG #18324: Duplicate value when I insert values in PK column |
| Previous Message | Christian Maurer | 2024-02-02 10:10:54 | Aw: BUG #18312: libpq: PQsetdbLogin() not thread-safe |