> 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 input to trigger the segfault (pipe to a f
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
retu
On Sat, Jan 21, 2023 at 12:50:37PM +, Gavin Smith wrote:
> On Thu, Jan 19, 2023 at 04:52:07AM +0100, Patrice Dumas wrote:
> > It is not completly clear to me that the performance cost would be lower
> > than looking at the commands stack and checking that the nesting is
> > valid, as there is,
On Thu, Jan 19, 2023 at 04:52:07AM +0100, Patrice Dumas wrote:
> It is not completly clear to me that the performance cost would be lower
> than looking at the commands stack and checking that the nesting is
> valid, as there is, in general, no deep nesting, and the performance
> penalty will proba
Links to discussion archive:
https://lists.gnu.org/archive/html/help-texinfo/2022-11/msg00060.html
https://lists.gnu.org/archive/html/help-texinfo/2022-11/msg00061.html
On Sun, Nov 27, 2022 at 02:39:25PM +0100, Patrice Dumas wrote:
> > What is more awkward is when there is no blank line before the
