Great fun and a good way to brush up on your assembly skills

Just load it on the debugger and leave your asm skill gather patina.

Well yes, that’s a pretty good way of debugging a third party app but if you are developing something you can have more ease with gdb attached

but you can follow any exception down to the exact line of code (or JNI call, I guess) where the problem occurs.

But, it’s not really where the problem occurred. How often do you get a stack trace and the bug fix is at the line referenced by the stack trace? Almost never. It’s more that it takes you down to the exact line of code where the effects of the problem are bad enough to affect the running of the program. But, the actual problem happened earlier, sometimes much earlier.

For example, NullPointerException isn’t actually the problem, it’s a symptom of the problem. Something didn’t get initialized properly, and nobody noticed for a while, until we tried to use it, and got a null pointer. Sometimes it’s easy to go from the effect (null pointer) to the cause (uninitialized thing). But, other times that “thing” was passed in, so you have to work backwards to try to figure out where that thing comes from, and why it’s in that broken state.

Sure, it’s better than nothing, but it’s still frustrating.

Super-advanced java devs like me do it like try{} catch (Exception e) { System.out.println("something went wrong); e.printStackTrace(); }

you can follow any exception down to the exact line of code

Which is usually not a piece of code written by us and is caused by another piece of code not written by us either

The same applies to using the core dump.

In fact, the Python one is the lest useful of the trio.

Ah, good old PlarformIO

If you are using systemd, there’s a tool called coredumpctl.

Nobody knows

you can set it

tl;dw: writes to the path in /proc/sys/kernel/core_pattern

I believe it’s /var/lib/apport/coredump on Ubuntu.

I meant faster than Python, not faster than Rust. Rust is fast.

I don’t know from where this legend comes from but lifetimes/concurrency/macros errors are brain-hurting.

Most of the time I find myself dropping project because I wrote my program in a correct way but Rust just does not like how it is designed lol. I can’t get shit done with this language

Rust compiler is passive agressive, like:

“There’s an error at line 286 because you still don’t know how to use the borrow checker after all this time ♥️”

except when it gives errors about lifetimes of some object.

boy, that makes my brain hurt

The rust compiler produces a flawless understanding of your code, and then quits out because understanding that code is a Nightly-only feature and you’re using the stable build.

Damn right. And once it compiles… it works.

I need a rust compiler in my life 😍

Raw adjust with tabs, fine adjust with spaces.

Don’t laugh, people are actually doing that.

Some people use tabs for indentation and spaces for alignment. It kind of gets the pros of tabs (user configurable indent-width) and the pros of spaces (alignment). That doesn’t work in Python where you can’t align stuff and the interpreter doesn’t allow mixing tabs with spaces, but in other languages it is a possible style.

Find me anyone who claims they use tabs for indentation, and I bet I’ll find at least one case where they’re using both tabs and spaces.

The only safe way to avoid war crimes is to avoid tabs.

And in Python, it’s merely a SyntaxCrime.

Runtime errors are still a thing.

tsoding’s channel is one I look forward to watching every single day, never a dull moment in his streams/videos.

If you’re someone who likes to watch things live, his Twitch channel is available here.

Good gods, a long-form content creator! Will be checking this out later