Incomplete stack on Windows

[daniel-white]

When tracking down a segfault, I got a stack trace that only appears to be the callback, and not the faulting stack:

PID 7492 received SIGSEGV for address: 0x13f23b0
SymInit: Symbol-SearchPath: '.;', symOptions: 530, UserName: 'administrator'
OS-Version: 6.1.7601 (Service Pack 1) 0x112-0x3
6C8228EC (segfault-handler): (filename not available): (function-name not available)
6C821617 (segfault-handler): (filename not available): (function-name not available)
773C223E (ntdll): (filename not available): RtlGetProcessHeaps
773AB806 (ntdll): (filename not available): RtlCaptureContext
773AB4C6 (ntdll): (filename not available): RtlMoveMemory
77360133 (ntdll): (filename not available): KiUserExceptionDispatcher

Any ideas why I can't see the offending stack?

[a-teammate]

Is this everything which got printed?
Since for me it shows some more lines, but only the addresses.

The fault is that the underlying library is searching for the .pdb files (containing the symbol informations on windows) in the wrong directories for me.
(or maybe the node grpc package - which is failing for me - is missing those I dont know).