Can you delay the printing so that GDB has a chance to start up before the console.log()? Getting a stack trace out of GDB would really be the best way to debug from here.
On Tuesday, January 15, 2019 at 3:26:58 AM UTC+1, Paul Spencer wrote: > > Hi, first post here and this may be the wrong spot but I've been unable to > find help elsewhere. I'm pretty much a n00b at this but here goes. I > maintain a node extension called node-mapserver > <https://github.com/pagameba/node-mapserver> which wraps mapserver > <https://mapserver.org/> so it can be used from javascript. I'm trying > to update it to support node 8 (from 4). I've got everything working > except I discovered by accident if I try to log one of the wrapped objects > using console.log it segfaults (where previously with Node 4 it didn't). > I've tried adding a toString method which works if I call it > (console.log(obj.toString()) but doesn't fix the segfault if I use > console.log(obj). So I guess my question is what do I need to add to my > objects so they don't segfault? I've tried using gdb to figure it out but > gdb just tells "During startup program terminated with signal SIGSEGV, > Segmentation fault." and I cannot get a backtrace. > > Cheers > > Paul > -- -- v8-users mailing list v8-users@googlegroups.com 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 v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
