为何用C语言setenv设置的环境变量无法通过Go的os.Getenv获取？

Hey, let's break down exactly what's happening here—this is a classic case of how Go and C handle environment variables under the hood differently:

The Core Issue #

When your Go program starts up, it makes a copy of the system's environment variables into its own internal map. All Go standard library functions like os.Getenv and os.Setenv operate directly on this map, not the global environ array that C's setenv/getenv uses.

• When you call os.Setenv, Go does two things: updates its internal map and syncs the change to the process's environ array. That's why C's getenv can see the GOSET variable just fine.
• But C's setenv only modifies the environ array—it has no idea about Go's internal map. So Go's os.Getenv keeps looking at its own outdated copy, which doesn't include CSET.

Quick Test to Confirm #

If you add this right after calling C's setenv, you'll see CSET isn't in Go's list of environment variables:

for _, envVar := range os.Environ() {
    fmt.Println(envVar)
}

Fixes You Can Use #

You've got two solid options here:

1. Use Go's os.Setenv instead
   If your use case allows it, just set the variable with Go's API. This ensures both Go and C see the same value, no extra work needed.

2. Manually sync Go's environment map
   If you absolutely have to use C's setenv, you can force Go to reload the environment from the environ array. Here's how:

   import "syscall"
   
   // After calling C.setenv...
   os.Clearenv() // Wipe Go's internal map
   // Reimport all variables from the process's environ
   for _, envStr := range syscall.Environ() {
       key, val, ok := strings.Cut(envStr, "=")
       if ok {
           os.Setenv(key, val)
       }
   }
   

   Now os.Getenv("CSET") will return the value you set via C.

Why Go Does This #

This design choice is all about performance and safety. Go's internal map lets environment variable operations run faster, and it prevents unexpected changes from C code messing with Go's state. The tradeoff is exactly this kind of cross-language sync issue when you mix C and Go environment variable calls.

内容的提问来源于stack exchange，提问作者dingrui