Re: Need to block SIGCHLD in libgc and guile internal threads

On Fri, Aug 29, 2014 at 10:36 AM, wrote: > On master, where we now require gc-7.2 or later, I guess we should be > able to simplify this and block all signals. > > However, it's not clear how to backport this to stable-2.0, which does > not even have a finalization thread, and yet gdb bug 17247 o

Re: Need to block SIGCHLD in libgc and guile internal threads

Doug Evans writes: > I think(!) I understand why gdb is hanging when used with libgc 7.4.x. > This is gdb bug 17247. > https://sourceware.org/bugzilla/show_bug.cgi?id=17247#c30 [...] > gdb/linux-nat.c calls sigsuspend when the inferior is running and gdb > needs to wait for it to stop. > gdb is

Re: Need to block SIGCHLD in libgc and guile internal threads

On Tue, Aug 26, 2014 at 1:14 AM, Doug Evans wrote: > Hi. > > I think(!) I understand why gdb is hanging when used with libgc 7.4.x. > This is gdb bug 17247. > https://sourceware.org/bugzilla/show_bug.cgi?id=17247#c30 > > First, libgc 7.4.x was the first release to default PARALLEL_MARK to > on, so

Need to block SIGCHLD in libgc and guile internal threads

Hi. I think(!) I understand why gdb is hanging when used with libgc 7.4.x. This is gdb bug 17247. https://sourceware.org/bugzilla/show_bug.cgi?id=17247#c30 First, libgc 7.4.x was the first release to default PARALLEL_MARK to on, so I'm guessing the same "bug" exists in 7.2, it's just not visible