Explore >> Select a destination
|
You are here 
|
marcan.st | ||
| | | | |
konradreiche.com
|
|
| | | | | Dave Cheney famously said it: cgo is not Go. You're not writing a Go program that uses some logic from a C library, instead you're writing a Go program that has to coexist with a belligerent piece of C code that is hard to replace, has the upper hand negotiations, and doesn't care about your problems. With cgo, C calls the shots, not your code. Today, I had to make this experience firsthand debugging a project that is using github.com/augustoroman/v8, a Go wrapper exposing a subset of v8's API natively written in C++. In a couple of test scenarios the program would just crash with the following C stack trace: | |
| | | | |
antonz.org
|
|
| | | | | Fake clock, new GC, flight recorder and more. | |
| | | | |
www.thanassis.space
|
|
| | | | | Stack-checking a program that will execute in orbit | |
| | | | |
www.jeremymorgan.com
|
|
| | | A quick look at my virtualization setup, remotely accessed headless VMs on a Linux Server. | ||
