Debugging memory corruption: who the hell writes "2" into my stack?

Re:Debugging memory corruption: who the hell writes "2" into... by saagarjha on Tuesday December 31, 2024 @11:04PM (#42563869)

> One of the greatest difficulties I've had in supporting Rust with Cosmopolitan Libc is that Rust libraries all try to be clever by using raw assembly system calls rather than using libc.

I’m sorry, this is coming from Justine “the magic syscall numbers are my god given right to use” Tunney?

[ Parent | on HN ]

Re:Debugging memory corruption: who the hell writes "2" into... by fc417fc802 on Tuesday December 31, 2024 @11:26PM (#42563949)

Seems like it depends entirely on context. I'd expect code which intends to be portable to use some sort of dynamically linked wrapper, even if that wrapper isn't libc.

[ Parent | on HN ]

Re:Debugging memory corruption: who the hell writes "2" into... by jart on Wednesday January 01, 2025 @07:20AM (#42565601)

It's the stated mission of my project. Rust's stated mission is memory safety.

So using raw system calls is a distraction for them.

[ Parent | on HN ]