Yep, that looks like a smoking gun to me.
-Kenton
On Mon, Nov 9, 2020 at 2:41 PM Zachary Dremann wrote:
> This looks related:
> https://lists.debian.org/debian-glibc/2014/01/msg00023.html
>
> I rebuilt everything in the same way on an ubuntu 16.04 VM, and I don't
> get the segfault. I don't
This looks related:
https://lists.debian.org/debian-glibc/2014/01/msg00023.html
I rebuilt everything in the same way on an ubuntu 16.04 VM, and I don't get
the segfault. I don't need to use fibers, so I'm okay to just avoid them.
On Friday, November 6, 2020 at 1:20:53 PM UTC-5
Hi Zachary,
It looks like the segfault is happening in glibc's backtrace() function
while gathering the stack trace for an exception. An exception is actually
expected here (the test case tests throwing an exception). Since it
happened specifically in fiber-related tests, my guess is that glibc's
I'm running on Ubuntu 14.04, 32 bit.
I have a custom g++ 10.1.0 as g++-10 installed in /usr/local, built from
source with no modifications or customizations
I cloned from master (commit 96936a7446164424d8f3f50430d83ee21f63f6a2), and
ran `autoreconf -fi`, then `./configure --without-openssl
