> If anyone notices Ruby programs which suddenly start to throw stack overflow errors (SystemStackError or the error message "stack level too deep") but *only* in the latest Rawhide (glibc >= 2.26-9000, ruby >= 2.5.0), then I'm interested to hear from you. I faced "stack level too deep" when running a unit test for rubygem-mysql2. As when I ran the case's logic it manually, that was okay, I just commented out the test case. https://src.fedoraproject.org/rpms/rubygem-mysql2/blob/master/f/rubygem-mysql2.spec#_154 https://github.com/rails/rails/blob/v5.0.0/activesupport/CHANGELOG.md stack level too deep error Jun On Thu, Jan 11, 2018 at 3:10 PM, Richard W.M. Jones <rjones@xxxxxxxxxx> wrote: > > OK I believe this is actually a bug in the nbdkit plugin rather than > glibc / Ruby. Apparently you need to call some functions to tell Ruby > about the thread stacks. Totally undocumented ... > > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > virt-p2v converts physical machines to virtual machines. Boot with a > live CD or over the network (PXE) and turn machines into KVM guests. > http://libguestfs.org/virt-v2v > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx -- Jun Aruga jaruga@xxxxxxxxxx IRC: jaruga, Office: TPB(Technology Park Brno) Building C 1F, Brno, Czech Republic _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
