On 21 January 2017 at 20:19, Hanno Böck <[email protected]> wrote: > The attached file will cause an out of bounds heap read access in the > function scan_node_contents. > > asan stack trace: > > ==12816==ERROR: AddressSanitizer: heap-buffer-overflow on address > 0x60200000dcff at pc 0x0000004969bf bp 0x7ffd18e99610 sp 0x7ffd18e98dc0 > READ of size 8 at 0x60200000dcff thread T0 > #0 0x4969be in __interceptor_memcmp.part.69 > (/old-ram1/texinfo/ginfo+0x4969be) > #1 0x5259db in scan_node_contents > /f/texinfo/trunk/info/info-utils.c:1694:29 > #2 0x54ca07 in info_node_of_tag_ext /f/texinfo/trunk/info/nodes.c:1447:11 > #3 0x54adb9 in info_node_of_tag /f/texinfo/trunk/info/nodes.c:1488:10 > #4 0x54adb9 in info_get_node_of_file_buffer > /f/texinfo/trunk/info/nodes.c:1112 > #5 0x54a5c3 in info_get_node_with_defaults > /f/texinfo/trunk/info/nodes.c:995:14 > #6 0x56de62 in dump_node_to_stream /f/texinfo/trunk/info/session.c:3764:10 > #7 0x56db32 in dump_nodes_to_file /f/texinfo/trunk/info/session.c:3727:11 > #8 0x531e19 in main /f/texinfo/trunk/info/info.c:1073:7 > #9 0x7faf0a4d878f in __libc_start_main (/lib64/libc.so.6+0x2078f) > #10 0x41a598 in _start (/old-ram1/texinfo/ginfo+0x41a598) >
I didn't reproduce this with the latest development version. Perhaps one of the other changes fixed the problem.
