Bug#597784: libv8-2.2.24: Segfault after errorious input using nodejs

It seems it is a nodejs bug, see http://groups.google.com/group/nodejs/browse_thread/thread/a7e5db68d4cd6356?hl=en Reassigning. Cheers, Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#597784: libv8-2.2.24: Segfault after errorious input using nodejs

An even simpler code snippet : new process.binding('evals').Script("a"); then wait several seconds doing nothing : segfault. The fact one has to wait might be a sign it's a gc bug, or a nodejs bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubs

Bug#597784: libv8-2.2.24: Segfault after errorious input using nodejs

Confirmed, i checked with latest v8 2.2.24.24 and, though it happens after many more inputs, it reproduces too. I'm going to check of this happens on the 2.3 branch. Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact

Bug#597784: libv8-2.2.24: Segfault after errorious input using nodejs

Package: libv8-2.2.24 Version: 2.2.24-5 Severity: normal Tags: upstream I accidentally wrote a javascript snipped with an errorious content; though what I noticed was that nodejs suddenly segfaulted. I've broken down the code to a snipped, that when ran manually in nodejs shell (segtest.js) a seg