Q: State of Debugging

[DanPartelly]

Hey,

Just some fast questions:

1. What is the state of debugging on Linux?
2. What notable debugging tools support Odin (Linux/Windows) gdb / lldb, valgrind, whatever.
3. What LLVM sanitizers / X-ray tooling are supported by Odin, if any.

With many thanks.

[Beefster09]

1. In my experience, not great. Best I've really gotten out of gdb is a stack trace without line numbers. Usually gets all sorts of confused when crossing language boundaries because the symbol table seems to be corrupted or something.
2. gdb kind of supports it
3. no idea

[z64]

In my experience, not great. Best I've really gotten out of gdb is a stack trace without line numbers. Usually gets all sorts of confused when crossing language boundaries because the symbol table seems to be corrupted or something.

In this scenario, are you building your odin code with -debug? What you describe sounds like behavior when you compile without debug info or with optimizations enabled (-o:speed, etc.)

[Beefster09]

I'm one of the users affected by the bug where compiling with debug creates a faulty binary (sometimes), so that's probably a big reason why gdb explodes even with debug symbols on.

[MarcusE1W]

I used lldb for my first time and I found it surprisingly helpful.
You can set break points, step line by line through the code and inspect variables.
There is probably more, but I have not figured that out yet.

[felipebueno]

I used lldb for my first time and I found it surprisingly helpful.

Yeah, me too! And lldb also offers a gui to make the debugging experience more enjoyable (if you prefer visual debuggers like me :)