News for hackers. Stuff that matters.
Re:Writing secure Go code by kccqzy on Tuesday November 05, 2024 @01:27PM (#42053984)
You missed the point.

> In any language, if you don't use a thread safe container and mutate it from multiple threads you'll get problems.

Yes I agree there will be problems but what kind of problems do you get? Can you potentially get a memory safety problem, or are you guaranteed that the problem is not a memory safety problem?

The point is that thread safety problems in Go lead to memory safety problems. That's not the case in Java. You can crash the whole Go program by doing that, but you cannot crash the JVM by doing the same thing.

Re:Writing secure Go code by yawaramin on Tuesday November 05, 2024 @06:09PM (#42056001)
Crashing the whole program is actually memory safety. Because then the program can't get into an undefined state where parts of the program have access to memory they shouldn't.
Re:Writing secure Go code by kccqzy on Tuesday November 05, 2024 @09:25PM (#42056849)
Crashing via SIGSEGV is not memory safety.
Re:Writing secure Go code by consteval on Wednesday November 06, 2024 @10:47AM (#42064085)
Crashing with SIGSEGV can be perfectly memory safe. For example, writing to a NULL address is defined behavior on almost all platforms and typically causes the OS to send SIGSEGV.