gjs should be producing a backtrace which should help. AFAIK there is no debugger at present.. seed has --seed-debug=all which gives you logs of most calls to introspection. but does not help much with JS errors. not sure if gjs has similar code.
Regards Alan --- On 11/Apr/2013, Denys Digtiar wrote: > Hi, > I've been playing with gjs in my spare time and encountered an error which > didn't have any information about where it originated. Naturally the > question arose, how do I pin point the source code which throwed this error? > > Is there anything like node debugger but for gjs? > What are other options except writing a bunch of print statements all over > the code? > > I am on Ubuntu 12.10, the version of gjs is 1.34.0 > > -- > with best regards, > Denys Digtiar _______________________________________________ javascript-list mailing list javascript-list@gnome.org https://mail.gnome.org/mailman/listinfo/javascript-list
