Hi, On Tue, 12 Nov 2024 at 14:45, Дмитрий Фролов <[email protected]> wrote: > It looks like this is a clang optimization issue. > > When environ is absent (not mentioned in the source code) > The value of envp is also 0x514000000040 (reproducible), > but the behavior may be each time different. > Mostly test fails with error, with or without ASAN report. > > Thus, it seems, that when environ variable is not used - > it`s being optimized, the corresponding memory is being > freed, but envp pointer still points to the freed memory.
* Oh, that's interesting. Could we maybe 'watch -l envp' in gdb(1) to see where it gets free'd? OR if there's another way to figure it out. (just checking) Thank you. --- - Prasad
