Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
runtime: Crash on package init with fatal error: bad pointer in write barrier #15831
When java loads the go library, it caused a crash:
Unfortunately it has only happened occasionally and I don't know how to reproduce it.
I believe this is related to #11689
referenced this issue
Jun 17, 2016
/cc @RLH, since this is also his territory, and I'll be out of town next week.
@balboah, which revision of github.com/google/gopacket are you at? (Specifically, I need to know what github.com/google/gopacket/layers/enums.go:381 refers to, since that line at HEAD clearly doesn't have any write barriers.)
It might also be relevant what revision of github.com/thisisnotourname/android-lib you're at.
Thanks, that revision does have a write barrier on line 381 (for my future reference: this line), which happens when writing the value part from the interface returned by
What do you mean by there being no "magic init" in android-lib?
Oh! 0x68686868 is a very specific "bad" pointer. That's the poisonStack value on 32-bit. I bet you just got unlucky and genuinely allocated something at that address. As far as I can tell, there's nothing preventing that from happening.
We haven't actually used poisonStack since April 2015, when we switched to 1-bit bitmaps for the stack (and lost the information we would need to poison the stack). I'm not sure if something used to prevent us from legitimately allocating at that address.
We should probably just remove poisonStack and the checks against that pointer.