News for hackers. Stuff that matters.
Re:Why Go Is Not Good by jjnoakes on Sunday June 29, 2014 @11:15PM (#7963515)
No, you are wrong.

First, mapping that page doesn't cause all null pointer dereferences to segfault.

And second, the language doesn't require a segfault. In fact, it explicitly permits the implementation to do whatever it likes.

That is the difference between safe and unsafe. It is in the language definition.

Re:Why Go Is Not Good by dbaupp on Monday June 30, 2014 @12:00AM (#7963635)
"the language"... which one? AIUI, Go doesn't state that null dereferences are undefined behaviour, but rather that they are guaranteed to panic.
Re:Why Go Is Not Good by richo on Monday June 30, 2014 @12:27AM (#7963696)
"The language" ?

C doesn't define behaviour of a null deref, but most compilers map a -rwx page there to ensure that attempts to deref fault.

In what circumstance do they not?

Re:Why Go Is Not Good by dbaupp on Monday June 30, 2014 @12:51AM (#7963743)
The compilers don't map pages there, the operating system does. The problem is the compiler will optimise assuming that a null deref never happens, so you can have source that looks like it should crash due to a null deref, but the compiler has "misoptimised" it to have very different behaviour.

http://blog.llvm.org/2011/05/what-every-c-programmer-should-...