Hey, and thanks for all the repleis! I was going to want to use --harmony, due to some weird crasht hat happens in my application. I am letting a v8 instance go into a new thread, so that my GUI app can handle stuff in the front, main thread. Everything works as expected - but when I am using a REPL (the v8 app i am talking about is nodejs) and wait a while, then I get a crash. But if I do the --harmony switch, everything works as expected. I have given the crash in my first email I think. But just in case I did not:
Ingwie@Ingwies-Air ~/Work/deskshell/mod_nodejs/out/Debug $ ./node ... Args: ./node Meep from contextify. > process.exit(); # # Fatal error in ../../deps/v8/src/global-handles.cc, line 274 # CHECK(state() != NEAR_DEATH) failed # ==== C stack trace =============================== 1: ?? 2: ?? 3: ?? 4: ?? 5: ?? 6: ?? 7: ?? 8: ?? 9: ?? 10: ?? Trace/BPT trap: 5 Ingwie@Ingwies-Air ~/Work/deskshell/mod_nodejs/out/Debug $ ./node --harmony ... Args: ./node Meep from contextify. > process.exit(); As you can see, when I use harmony, things work as expected. The debugger bugs the hell out when I try to debug that. I get stopped due to SIGTTIN and SIGTTOU. When I disable these two signals (setting stop, notify and such to false), then the debugger just hangs, and whatever I do, nothing is shown in the terminal form my typing, like STDIN was disabled for some reason o.o So, i cant really seem to debug this. What do you think is the problem here? Kind regards, Ingwie Am 26.03.2014 um 10:51 schrieb Andreas Rossberg <[email protected]>: > On 26 March 2014 10:38, Jakob Kummerow <[email protected]> wrote: >> For the record, I would recommend not to enable --harmony by default. >> There's a reason this flag exists: the features it enables are generally not >> ready for prime-time yet. While some might be very close to what will be >> enabled by default at some point, others may be crashy, buggy, incomplete, >> or expected to change in behavior. > > It might even contain functionality that will be taken out again. And > fixing bugs with these features, even critical ones, has lower > priority. You are on your own. > > However, you are invited to try the new --es-staging flag that we > introduced recently. It is a safer alternative: it only activates > features that are complete, stable, and (almost) ready for prime time. > Anything moved there is on the way to being turned on by default after > some period of testing. > > /Andreas -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
