News for hackers. Stuff that matters.
Re:Why would you still want to use strace in 2023? [video] by angra_mainyu on Monday January 08, 2024 @10:18AM (#38913144)
that's strange, I've been working professionally in Go for years and two things happen:

1) what are exceptions in many languages are plain errors in Go 2) a defer-recover block is usually put at the very top of a risky call

This covers 99% of sources of panics.

Now, the one that truly does mess you up is when it comes from CGO/calling out to C. That will tear your application and there is nothing you can do about it.

Re:Why would you still want to use strace in 2023? [video] by cwillu on Monday January 08, 2024 @11:11AM (#38914071)
I wish they paniced. I'm talking about trees of function calls with variations on “err = thing(); if err: return err” multiple times in a function, so receiving an error code in the root function tells you very little about what went wrong or where it went wrong.
Re:Why would you still want to use strace in 2023? [video] by gpderetta on Monday January 08, 2024 @03:09PM (#38917400)
Exactly! Throwing away the call stack before deciding how to handle the error is not ideal.
Re:Why would you still want to use strace in 2023? [video] by angra_mainyu on Thursday January 11, 2024 @01:34PM (#38956545)
I've honestly never needed it when dealing an error, the fact that errors are handled near where they occur means a stack is rarely needed.

If you bubble up errors a lot then errors.Is/As is made for that purpose.

You really only care about a stack trace with a panic.

In anycase, runtime.Stack() iirc should return the stack.

But this sounds more like trying to write other languages in Go rather than writing in Go.