Callstack for fatal errors is just ??? | Zig Programming Language | Page 1

wise cave Nov 10, 2023, 2:37 PM

#

My callstacks for any errors look like

thread 19812 panic: integer overflow
???:?:?: 0x7ff6cef213dc in ??? (???)
???:?:?: 0x7ff6cef2269c in ??? (???)
???:?:?: 0x7ff6cef992b5 in ??? (???)
???:?:?: 0x7ff6cef9931b in ??? (???)
???:?:?: 0x7ffcd906257c in ??? (KERNEL32.DLL)
???:?:?: 0x7ffcda90aa77 in ??? (ntdll.dll)

despite having debug as a target. Is that expected?

#

(And yes, the fatal is within my code and reproducible)

wise cave Nov 10, 2023, 8:36 PM

#

Any ideas?

split thorn Nov 10, 2023, 9:26 PM

#

thats what you get when debug symbols are borked

#

is the .pdb file there

#

and the pdb file needs to be in the same location as the executable.

wise cave Nov 10, 2023, 9:45 PM

#

theres a pdb next to the exe

split thorn Nov 10, 2023, 9:56 PM

#

idk works fine for me.
Make an empty project with zig init-exe in an empty folder and use this as your zig main.

const std = @import("std");

pub fn stacktracer(n: usize) void {
    if (n == 0) @panic("WTF!");
    stacktracer(n - 1);
}

pub fn main() !void {
    stacktracer(20);
}

then run zig build run

wise cave Nov 10, 2023, 10:02 PM

#

yup getting a stacktrace

#

Hmm, in that specific project, I'm using some external c libs

#

maybe thats the reason?

#

its the only difference I could think of, besides having a custom build.zig

split thorn Nov 10, 2023, 10:08 PM

#

idk maybe something is borked and debug symbols arent being emitted. I'd double check your work

#

particularly your build stuff

wise cave Nov 10, 2023, 10:23 PM

#

is there any command to clean all cache files recursively?

#

I've copied over most of my stuff into the test project, yet the stack trace still works

#

oh i found the culprit

#

but this looks like a zig bug

#Callstack for fatal errors is just ???