Key creation problem with 2.1.16

[Carola Grunwald]

Hi!

On Mon, 30 Jan 2017 17:52:44 +0100, Justus Winter wrote:

>Carola Grunwald <caro at nymph.paranoici.org> writes:
>
>> on Mon, 30 Jan 2017 10:50:53 +0100, you wrote:
>>
>>>Carola Grunwald <caro at nymph.paranoici.org> writes:
>>>
>>>> agent the call stack dump always looks the same as shown below. Here it
>>>[...]
>>>> Stack for thread gpg-agent.exe+0x14e0
>>>> -------------------------------------------------
>>>> ntoskrnl.exe!SeAccessCheckWithHint+0xb4a
>>>
>>>May I ask how you create these stack traces?
>>
>> Sysinternals Process Explorer v16.20
>> https://technet.microsoft.com/en-us/sysinternals/processexplorer
>
>How did you get it to resolve symbols?  I never figured that out :/

These are the out-of-the-box results. There are no further Windows
debugging tools or symbol packages installed.

>
>> You know of anything more accurate I could use?
>
>Well, you can attach a gdbserver to the process, and use gdb on a remote
>Linux box with the sources, that is really nice, albeit a bit slow.

I think that's beyond my skills. Let that do those who know about gpg's
internals.

>
>> BTW, the problem persists after updating to 2.1.18, same dumps.
>
>:/
>
>Fwiw, I saw gpg-agents hanging on Windows XP, it regularly happened
>while running the test suite.  I don't see those kind of problems with
>our current Windows 8.1 test box.

Sorry, for privacy reasons I banned Windows 8 ff. here. I can't imagine
why it should do any better.

And there's no reason to run any test suite. Just start the agent and
wait. In the end there'll be two blocked libnpth-0 dlls.

Their threads' call stack dumps:

ntoskrnl.exe!SeAccessCheckWithHint+0xb4a
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x7d2
ntoskrnl.exe!KeWaitForMutexObject+0x19f
ntoskrnl.exe!PsIsSystemProcess+0x94
ntoskrnl.exe!KeStackAttachProcess+0x11c1
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x9dd
ntoskrnl.exe!KeWaitForMutexObject+0x19f
ntoskrnl.exe!NtWaitForSingleObject+0xb2
ntoskrnl.exe!KeSynchronizeExecution+0x3a43
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x690
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x484
wow64.dll!Wow64SystemServiceEx+0x1ce
wow64.dll!Wow64LdrpInitialize+0x429
ntdll.dll!LdrGetProcedureAddress+0x24127
ntdll.dll!LdrInitializeThunk+0xe
ntdll.dll!NtWaitForSingleObject+0x15
ntdll.dll!RtlIntegerToUnicodeString+0x20b
libnpth-0.dll!npth_clock_gettime+0x18f
libnpth-0.dll!npth_protect+0x1b
gpg-agent.exe+0x1594
libassuan-0.dll!assuan_get_assuan_log_prefix+0x169b
libassuan-0.dll!assuan_socket_connect+0x47e
gpg-agent.exe+0x1e5c
ntdll.dll!RtlInitializeExceptionChain+0x63
ntdll.dll!RtlInitializeExceptionChain+0x36

and

ntoskrnl.exe!SeAccessCheckWithHint+0xb4a
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x7d2
ntoskrnl.exe!KeWaitForMutexObject+0x19f
ntoskrnl.exe!PsIsSystemProcess+0x94
ntoskrnl.exe!KeStackAttachProcess+0x11c1
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x9dd
ntoskrnl.exe!KeWaitForMutexObject+0x19f
ntoskrnl.exe!NtWaitForSingleObject+0xb2
ntoskrnl.exe!KeSynchronizeExecution+0x3a43
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x690
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x484
wow64.dll!Wow64SystemServiceEx+0x1ce
wow64.dll!Wow64LdrpInitialize+0x429
ntdll.dll!LdrGetProcedureAddress+0x24127
ntdll.dll!LdrInitializeThunk+0xe
ntdll.dll!NtWaitForSingleObject+0x15
mswsock.dll+0x678c
mswsock.dll+0x461c
libassuan-0.dll!__assuan_read+0x11f
libassuan-0.dll!assuan_free+0x3a2
libassuan-0.dll!assuan_get_assuan_log_prefix+0xd4f
libassuan-0.dll!assuan_get_assuan_log_prefix+0x1dc9
libassuan-0.dll!assuan_sock_check_nonce+0x21
gpg-agent.exe+0x2bfc
ntdll.dll!RtlInitializeExceptionChain+0x63
ntdll.dll!RtlInitializeExceptionChain+0x36

with gpg-agent.exe:

ntoskrnl.exe!SeAccessCheckWithHint+0xb4a
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x7d2
ntoskrnl.exe!KeWaitForMutexObject+0x19f
ntoskrnl.exe!PsIsSystemProcess+0x94
ntoskrnl.exe!KeStackAttachProcess+0x11c1
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x9dd
ntoskrnl.exe!KeWaitForMutexObject+0x19f
ntoskrnl.exe!NtWaitForSingleObject+0xb2
ntoskrnl.exe!KeSynchronizeExecution+0x3a43
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x690
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x484
wow64.dll!Wow64SystemServiceEx+0x1ce
wow64.dll!Wow64LdrpInitialize+0x429
ntdll.dll!RtlResetRtlTranslations+0x1b08
ntdll.dll!RtlResetRtlTranslations+0xc63
ntdll.dll!LdrInitializeThunk+0xe
ntdll.dll!NtWaitForSingleObject+0x15
ntdll.dll!RtlIntegerToUnicodeString+0x20b
libnpth-0.dll!npth_clock_gettime+0x18f
libnpth-0.dll!npth_eselect+0x485
gpg-agent.exe+0x374b

A thread safety problem with the Assuan library?
Just guessing. ;)

Kind regards

Caro