cant go backwards in debugger

it's 2016 and you still can't go back in gdb.

i want to debug a crash, i crashed in function f so i want to step back a bit to see which function called f.

can't do it. not happening. computers are not advanced enough yet.

gotta put breaks around everything that calls f and re run, skipping working calls until I hit the breaking one.

This is the modern workflow?

That's just because C is shit. There is nothing gdb can do about it when the language is inherently flawed. OTOH LISP debuggers were able to step back ten years before C was even invented.

Get a load of this guy, can't even reverse time!

>>2
Unfair comparison: when you debug lisp with slime you are evaluating sexps, when you debug a c compiled binary with gdb you are running cpu instructions. Also, I don't think lithp debuggers were that sophisticated back in the 70s.

The fuck kind of question even is this? Nigger.

I think gdb is a pretty cool guy. Eh never walks back and doesn't afraid of crashes.

>>1
https://www.gnu.org/software/gdb/news/reversible.html

GDB is a piece of shit, but your problem can easily be solved by the bt command. Run your program in it, let it crash, issue bt when it does.

delete Cudder;