Hello, Again, our new fuzzer found a SEGV error in bison 3.8.2. It is similar to the previous bug report, however the stack trace is quite different.
Stack Trace ==4348==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x555c875fb719 bp 0x7ffeda9c35e0 sp 0x7ffeda9c3470 T0) ==4348==The signal is caused by a READ memory access. ==4348==Hint: address points to the zero page. #0 0x555c875fb718 in quotearg_buffer_restyled lib/quotearg.c:393 #1 0x555c875fc4ca in quotearg_n_options lib/quotearg.c:899 #2 0x555c875fc913 in quotearg_n_style lib/quotearg.c:950 #3 0x555c87527783 in boundary_print src/location.c:149 #4 0x555c8752788d in location_print src/location.c:164 #5 0x555c87562d48 in yy_symbol_print src/parse-gram.c:1390 #6 0x555c8756be4e in gram_parse src/parse-gram.c:3099 #7 0x555c875847e3 in reader src/reader.c:766 #8 0x555c8752fbe0 in main src/main.c:118 Steps to Reproduce We configured and built bison with address sanitizer: CFLAGS="-fsanitize=address -g -O0" ./configure make -j Then, run bison with: ./bison <attached_file> -T Environment - OS: Ubuntu 18.04.1 - gcc 7.5.0 - bison: 3.8.2 Many Thanks, Youngseok Choi
<<attachment: bison_input_poc2.zip>>