Re: [capnproto] Assert in exception.c++ triggering only in ASAN

I guess this means that under ASAN, the stack is not allocated in the traditional way. For some reason there's a 1MB offset between where the ExceptionCallback was allocated and where a local variable inside its constructor was allocated. The check there is pretty hacky and probably technically

[capnproto] Assert in exception.c++ triggering only in ASAN

I'm seeing this assert trigger in exception.c++ when run on ASAN on our (admittedly old) Linux boxes: KJ_ASSERT(offset < 65536 && offset > -65536, "ExceptionCallback must be allocated on the stack."); The value of offset is 1048864. Is this code perhaps relying on some construct