On Fri, Oct 29, 2021 at 10:41 AM Luca Olivetti via lazarus < lazarus@lists.lazarus-ide.org> wrote:
> > I now tested under windows 10 64 bits (the exe is 32 bits, the previous > test was under windows 7 32 bits), and here instead of stopping once in > ntdll!RtlpNtMakeTemporaryKey it stops twice: in ntdll!RtlZeroHeap and in > ntdll!RtlCaptureStackContext. > The former (RtlZeroHeap) shows what it seems a bogus call stack (i.e. > just two levels, the RtlZeroHeap itself and 00000000). > Searching around seems to suggest that RtlpNtMakeTemporaryKey is typically part of a stack trace involving memory/stack corruption or freeing an invalid reference or already freed pointer. See this example: https://stackoverflow.com/questions/45162248/calling-free-in-c-triggers-ntdlldbgbreakpoint-in-debug-but-crashes-in-rel/45247035 Since the code writes something to memory in the int3 branch, check errno to see if that reveals something.
-- _______________________________________________ lazarus mailing list lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus