Hi Thanks for the response; the reason that i rushd to this group was that i actually thought i had opend an irrelevant issue to Node.js; if you claim it actually is relevant, then so be it :) my apologies for causing confusion
On Friday, March 25, 2016 at 10:15:43 AM UTC-4, Ali Sheikh wrote: > > I would suggest continuing to triage this on the Node.js issue tracker > until the root cause is clearer. I can help on the node.js issue tracker. > > On Fri, Mar 25, 2016 at 6:22 AM, Yholli Konnonikoola <[email protected] > <javascript:>> wrote: > >> Hello >> >> this is the issue i filed on https://github.com/nodejs/node/issues/5900; >> turns out it might not be node but v8 >> <https://github.com/nodejs/node/labels/v8> so i thought this might be >> the correct location to report it: >> >> >> while fiddling with the toy js parser I have made, i came across weird >> 139 (that is, Segmentation fault) errors which are driving me nuts. I've >> pruned every unnecessary part of the parser and looks like i have been able >> to is >> >> Hello >> while fiddling with the toy js parser I have made, i came across weird >> 139 (that is, Segmentation fault) errors which are driving me nuts. I've >> pruned every unnecessary part of the parser and looks like i have been able >> to isolate the error-causing case. i have very little experience using >> debugging tools to delve in this issue all by myself; i would hence be glad >> if someone could help me find out what is going on . >> >> the faulty case: https://github.com/icefapper/lubejs >> meminfo: https://gist.github.com/icefapper/3081ce0e4f1e8bb17314 >> my sys is : Linux 3.13.0-37-generic #64 >> <https://github.com/nodejs/node/issues/64>-Ubuntu SMP Mon Sep 22 >> 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux (specifically it is LM >> 17.1) >> cpuinfo: https://gist.github.com/icefapper/5dc357ab7d751a7ceb86 >> >> i have been experiencing it on 5.6.0 and up (i.e, even with the latest >> stable 5.9.* which i even built from source) >> >> Thanks a lot reading this far, and I hope you could reproduce the error >> case. Simply run the "run.sh" thing 40-times or so, and the read the >> "lubelean.log"; please note, though, that the "lubelean.log" already >> contains the logs I received by running 'run.sh' which means if you need >> your own logs, you must delete it and *then* run 'run.sh'. >> >> olate the error-causing case. i have very little experience using >> debugging tools to delve in this issue all by myself; i would hence be glad >> if someone could help me find out what is going on . >> >> the faulty case: https://github.com/icefapper/lubejs >> meminfo: https://gist.github.com/icefapper/3081ce0e4f1e8bb17314 >> my sys is : Linux 3.13.0-37-generic #64 >> <https://github.com/nodejs/node/issues/64>-Ubuntu SMP Mon Sep 22 >> 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux (specifically it is LM >> 17.1) >> cpuinfo: https://gist.github.com/icefapper/5dc357ab7d751a7ceb86 >> >> i have been experiencing it on 5.6.0 and up (i.e, even with the latest >> stable 5.9.* which i even built from source) >> >> Thanks a lot reading this far, and I hope you could reproduce the error >> case. Simply run the "run.sh" thing 40-times or so, and the read the >> "lubelean.log"; please note, though, that the "lubelean.log" already >> contains the logs I received by running 'run.sh' which means if you need >> your own logs, you must delete it and *then* run 'run.sh'. >> >> >> Sincerely, >> >> Neni >> >> -- >> -- >> v8-dev mailing list >> [email protected] <javascript:> >> http://groups.google.com/group/v8-dev >> --- >> You received this message because you are subscribed to the Google Groups >> "v8-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Ali > -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" 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.
