Leopold Toetsch wrote: > It might be on the stack or just in a CPU register. While we have > code to mark all possible pointers on the stack, this isn't generally > true for CPU registers, as that's rather system-dependent. > > See also src/cpu_dep.c():trace_system_areas() If we can't rely on trace_system_areas to mark C variables, why have it in the first place? It probably only obscures bugs on other platforms, making it harder to port.
> leo > -- Bram Geron | GPG 0xE7B9E65E
