hyc@symas.com writes:

This looks like a pretty major compiler bug, assuming the trace is correct.

Not necessarily, valid optimizations can rearrange memory beyond a debugger's ability to figure out what's going on. Still, this does look like a strange optimization if it's a valid one.

What version of compiler did you use, were you using optimization? Can you try with a different version and/or without optimization?