[Nasm-bugs] [Bug 3392776] uninitialized value use

noreply-nasm at dev.nasm.us noreply-nasm at dev.nasm.us
Sun Oct 17 07:34:00 PDT 2021


--- Comment #2 from Cyrill Gorcunov <gorcunov at gmail.com> ---
Thanks a huge for such deep analysis, Adnrew! Since I don't have this sanitizer
installed and my local gcc's sanitizer doesn't reveal anything I did a hack:
initialized new memory with poison value and put asserts() on access. In result

> value 55555555
> nasm: asm/parser.c:983: parse_line: Assertion `value[1].type != 0x55555555' failed.

which means we indeed read uninitialized data. I suspect that using memset
would do a trick but same time I think it will be just a workaround, it looks
like we missing terminal symbol somewhere here. Need to think about...

Thanks again, and I'm really-really sorry for such long replies from my side, I
very appreciate your work!

You are receiving this mail because:
You are watching all bug changes.
You are on the CC list for the bug.

More information about the Nasm-bugs mailing list