GeneralPurposeAllocator: No stack trace for memory leak on Windows

[lxn]

The code below produces just the output Memory leak detected: on Windows, missing the stack trace.

const std = @import("std");

pub fn main() anyerror!void {
    var gpa = std.heap.GeneralPurposeAllocator(.{}){};
    defer _ = gpa.deinit();
    const allocator = &gpa.allocator;

    _ = try allocator.alloc(u8, 1);
}

[nektro]

example of the intended output from linux

$ zig run test.zig 
error(gpa): memory address 0x7f801f995000 leaked: 
./test.zig:8:28: 0x22826e in main (test)
    _ = try allocator.alloc(u8, 1);
                           ^
/home/meg/.local/share/zig/lib/std/start.zig:581:37: 0x22195a in std.start.callMain (test)
            const result = root.main() catch |err| {
                                    ^
/home/meg/.local/share/zig/lib/std/start.zig:515:12: 0x20880e in std.start.callMainWithArgs (test)
    return @call(.{ .modifier = .always_inline }, callMain, .{});
           ^
/home/meg/.local/share/zig/lib/std/start.zig:425:17: 0x2076e6 in std.start.posixCallMainAndExit (test)
    std.os.exit(@call(.{ .modifier = .always_inline }, callMainWithArgs, .{ argc, argv, envp }));
                ^

[nekrondev]

I always run into this when developing for my company (windows based infrastructure) and have to do the debugging of memory leaks on some Linux based server.

So why is the output of the memory trace invisible for windows? Is the output piped to wrong fd?

[svc-user]

Upon initializing the GeneralPurposeAllocator you can set the stack_trace_frames field of the config to iirc at least 32 on windows to get a stack trace. As a workaround,ofc.

[squeek502]

Upon initializing the GeneralPurposeAllocator you can set the stack_trace_frames field of the config to iirc at least 32 on windows to get a stack trace. As a workaround,ofc.

Thanks for mentioning this, made it much easier to figure out what was going wrong (#11885).