To whom it may concern, I have found a crash and segfault in texinfo (info).
Here is how you reproduce the segfault. ``` cat /dev/urandom | info ``` It usually gives the return code 139 for segfault and displays the "Segmentation fault (core dumped)" message, however sometimes it gives the return code 0 without the message. Running the line to reproduce will likely show a segfault within 5 tries. Note: The executable `info` 7.0 shipped with my package manager does Segfault in gdb, however when I installed `info` from source at https://ftp.gnu.org/gnu/texinfo/, it does not segfault in the debugger but it still does segfault when run without the debugger. Crashes ======= | name | crash in gdb? | crash when run without gdb | |------------------+---------------+----------------------------| | From source v7.0 | No | Yes | | From pacman v7.0 | Yes | Yes | Since the version shipped with my package manager is not compiled with -g debug symbols, I was not able to find the source of this segfault. ``` Program received signal SIGSEGV, Segmentation fault. 0x00007ffff7e9884d in ?? () from /usr/lib/libc.so.6 (gdb) bt #0 0x00007ffff7e9884d in ?? () from /usr/lib/libc.so.6 #1 0x0000555555578344 in ?? () #2 0x000055555557e613 in ?? () #3 0x00005555555630f4 in ?? () #4 0x0000555555563305 in ?? () #5 0x00005555555754f8 in ?? () #6 0x000055555556bef9 in ?? () #7 0x000055555555d24c in ?? () #8 0x00007ffff7d68290 in ?? () from /usr/lib/libc.so.6 #9 0x00007ffff7d6834a in __libc_start_main () from /usr/lib/libc.so.6 #10 0x000055555555dc85 in ?? () ``` Here is part of the output of uname -a ``` Linux 6.0.9-arch1-1 x86_64 GNU/Linux ``` Best, Jake Roggenbuck
