Re: Segfault in texinfo

[Sam James]

> On 21 Jan 2023, at 21:35, jake roggenbuck <roggenbuckjake@gmail.com> wrote:
> 
> 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
> ```
> 

Please capture some exact input to trigger the segfault (pipe to a file first, 
then test it after by piping into 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.
> 
Please consult the documentation for your distribution to try adding it.

signature.asc
Description: Message signed with OpenPGP