[email protected] (Niels Möller) skribis: > [email protected] (Ludovic Courtès) writes: > >> --8<---------------cut here---------------start------------->8--- >> $ lshg -G fencepost.gnu.org >> Passphrase for key `xxx@yyy': >> Aborted >> --8<---------------cut here---------------end--------------->8--- >> >> A look at the strace output suggests an assertion failure in one of the >> child processes: >> >> --8<---------------cut here---------------start------------->8--- >> write(2, "lshg: sys.c:109: sys_on_fd: Assertion `((void *)0) == >> sys->files[fd][ev].f && \"multiple handlers registered for a file event\"' >> failed.\n", 135) = 135 >> --8<---------------cut here---------------end--------------->8--- >> >> Any ideas? > > It looks like lshg sets the close-on-exec flag on the stdio file > descriptors, before execing lsh. Which maybe is why you don't get to see > that assertion failure message. > > Can you try the following patch? To be applied to the branch > "lsh-2.0.4".
I confirm solves the problem, thanks! Ludo’. _______________________________________________ lsh-bugs mailing list [email protected] http://lists.lysator.liu.se/mailman/listinfo/lsh-bugs
