On Sun, Jan 22, 2023 at 06:57:22AM +, Sam James wrote:
>
>
> > On 21 Jan 2023, at 21:35, jake roggenbuck wrote:
> >
> > To whom it may concern,
> >
> > I have found a crash and segfault in texinfo (info).
> >
> > Here is how you reproduce
> On 21 Jan 2023, at 21:35, jake roggenbuck 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 inpu
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
On 20 March 2016 at 19:21, Thomas Klausner wrote:
> I've just debugged a segfault I encountered with texinfo-6.1 on
> NetBSD-7.99.26/amd64 when translating some files that lilypond-2.18.2
> provides
> (http://download.linuxaudio.org/lilypond/sources/v2.18/lilypond-2.18.2.tar.gz).
>
> I tracked th
Hi!
I've just debugged a segfault I encountered with texinfo-6.1 on
NetBSD-7.99.26/amd64 when translating some files that lilypond-2.18.2
provides
(http://download.linuxaudio.org/lilypond/sources/v2.18/lilypond-2.18.2.tar.gz).
It happens in makeinfo. When running gdb on perl I see this:
(gdb) r
