My dear followers, are you in the right headspace to receive information about the Golang GC that could possibly hurt you?
-
-
Replying to @erikcorry
Bring it on. Nothing in GCs can hurt me more than it already did. Or so I think.
2 replies 0 retweets 8 likes -
Replying to @shipilev
Sorry I don't have anything new for _you_. I just like the expression and it made me think of the GC ballast blog post and tearing fat pointers. You're cheating anyway because you weren't one of my followers when I wrote the tweet :-) https://en.wikipedia.org/wiki/Go_(programming_language)#Lack_of_race_condition_safety …
1 reply 0 retweets 5 likes -
Replying to @erikcorry
Oh, so you are about to say that Golang GC is not safe under the races? That would be new for me!
1 reply 0 retweets 1 like -
Replying to @shipilev
That's the sort of thing I might say, yes, but only if your headspace is ready.
1 reply 0 retweets 0 likes -
Replying to @erikcorry
Oh please, I have been already educated that Swift's ARC corrupting the heap under the race (just like GC Handbook predicted it should) is okay and should not be the cause for concern. Seeing a tracing GC designed to fail the similar way would be interesting.
1 reply 0 retweets 6 likes -
Replying to @shipilev
I did not know that! <the unplumbed depths of the human soul become visible> Apparently Go's memory safety in race conditions is "not a problem in practice" because they have a race detector.
3 replies 0 retweets 3 likes -
Replying to @erikcorry @shipilev1 reply 0 retweets 0 likes
-
Replying to @erikcorry @shipilev2 replies 0 retweets 0 likes
-
Replying to @erikcorry
Ugh. I wonder if this is still true today! Having critical metadata spanning multiple words is downright odd, and basically quality-of-implementation issue. Hotspot does a few sacrifices to avoid this (e.g. aligning objects by 8 to have aligned headers).
2 replies 0 retweets 1 like
Yes, it is still true today. The Go developers refuse to fix it even after a CTF came out in which contestants exploited a Go program using the technique I described there.
-
-
"refuse", lol. What a disingenuous statement. If you had attacker controlled Go code, you could just type the word unsafe and trivially create such an "exploit".
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.