Thank you for suggestion Rui, I figured out the place which were eating the stack (re-throwing Error with only message copied). And then found the place which threw the original Error. It is unfortunate though that there is no way to debug the standalone GJS application. I heard about LookingGlass but if I understand it correctly it works only for gnome-shell.
On Thu, Apr 11, 2013 at 5:30 PM, Rui Tiago Cação Matos <tiagoma...@gmail.com > wrote: > On 11 April 2013 01:32, Denys Digtiar <due...@gmail.com> wrote: > > What are other options except writing a bunch of print statements all > over > > the code? > > To get a JS backtrace: > > log(new Error().stack); > > or just use the current error object if inside a catch block. Not a > debugger but helps quite a bit IME. > > Rui > -- with best regards, Denys Digtiar
_______________________________________________ javascript-list mailing list javascript-list@gnome.org https://mail.gnome.org/mailman/listinfo/javascript-list
