Antonio Terceiro dijo [Wed, Dec 07, 2022 at 03:29:41PM -0300]:
> > > (And just to be on the safe side, maybe you could do a memory test
> > > to exclude a hardware failure.)
> >
> > OK -- I cannot say I'll do a memtest right now, as this is a
> > productive machine, but will do it soon-ish ☺
> >
On Wed, Dec 07, 2022 at 09:36:26AM -0600, Gunnar Wolf wrote:
> Bernhard Übelacker dijo [Wed, Dec 07, 2022 at 03:14:40PM +0100]:
> > Dear Gunnar,
> > I tried to collect some more information for the Maintainer.
>
> Thanks!
>
> > First I need to create a .irbrc with the USE_SINGLELINE
> > set to tr
Bernhard Übelacker dijo [Wed, Dec 07, 2022 at 03:14:40PM +0100]:
> Dear Gunnar,
> I tried to collect some more information for the Maintainer.
Thanks!
> First I need to create a .irbrc with the USE_SINGLELINE
> set to true, to reach any function in libedit/readline.
>
> Next I tried to reach the
Dear Gunnar,
I tried to collect some more information for the Maintainer.
First I need to create a .irbrc with the USE_SINGLELINE
set to true, to reach any function in libedit/readline.
Next I tried to reach the address given in _IO_new_file_overflow,
but was not able to. This might be related t
Package: ruby3.0
Version: 3.0.4-8
Severity: normal
I often use irb for many quick checks in my system. I was quite amazed
to find the segfault I am attaching; I was unable to reproduce it, but
still, I believe it to be worth reporting. It seems to come from
_something_ in the call to the C functio
