purego

The dynamic linking story in Go is complicated at best, particularly if you shun cgo, because you commonly need to cgo into ld.so to use dynamic linking. But there's this if you wanna try: https://github.com/ebitengine/purego

Also interesting project to point out since we discuss DNS and LDAP, nsswitch here: A library for calling C functions from Go without Cgo. https://github.com/ebitengine/purego https://news.ycombinator.com/item?id=34763681

In the malware reverse engineering scene, there are a lot of forks of the upstream "debug" go library, because it allows loading, parsing, compiling and executing libraries from disk (rather than in-kernel or in-userspace) because it is independent of dlopen. And there's also "purego" as an implementation that directly generates shellcode. Maybe those will help you, too? I am just mentioning these because for my use cases those approaches worked perfectly, CGO free. [1] https://github.com/Binject/debug [2] https://github.com/ebitengine/purego

I thought I had a piece of dust on my screen, but as I scrolled the dust scrolled: what do these 0xB7 characters do in the identifiers? Are they just "name mangling" to keep them from being exported or something? https://github.com/ebitengine/purego/blob/v0.2.0-alpha/sys_d... I noticed another 0xB7 character in a comment, and sure enough it seems to be part of the identifiers: https://github.com/ebitengine/purego/search?q=runtime%C2%B7c...