Explore >> Select a destination
|
You are here 
|
davidgow.net | ||
| | | | |
jmmv.dev
|
|
| | | | | In a recent work discussion, I came across an argument that didn't sound quite right. The claim was that we needed to set up containers in our developer machines in order to run tests against a modern glibc. The justifications were that using LD_LIBRARY_PATH to load a different glibc didn't work and statically linking glibc wasn't possible either. But... running a program against a version of glibc that's different from the one installed on the system seems like a pretty standard requirement, doesn't it?... | |
| | | | |
danielmangum.com
|
|
| | | | | This is part of a series on the blog where we explore RISC-V by breaking down real programs and explaining how they work. You can view all posts in this series on the RISC-V Bytes page. Today we are going to take a brief detour from our previous posts in this series and look at Rust Cross-Compilation for RISC-V. This will be a shorter post focused on providing useful information about how rustc works, as well as offering exact steps and configuration to target RISC-V when compiling your Rust programs. | |
| | | | |
blog.quarkslab.com
|
|
| | | | | [AI summary] The blog post discusses the implementation of a hooking mechanism for Go programs, focusing on the challenges of intercepting function calls and managing concurrency issues. The approach involves modifying the execution flow of Go functions by inserting custom assembly code to handle stack pivoting, ABI switching, and register saving. This allows for the integration of C functions within Go code while addressing platform-specific limitations and concurrency problems. The post highlights the complexity of working with Go's internal structures and the benefits of using Go for hooking, as it simplifies the manipulation of Go types and data structures. | |
| | | | |
www.sysdig.com
|
|
| | | |||
