On 09/18/2013 11:20 AM, David Prévot wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
[ Replying back the actual bug report. ]
Hi Jon,
Le 17/09/2013 22:55, Jon a écrit :
On 09/17/2013 05:20 PM, David Prévot wrote:
On Sun, Sep 23, 2012 at 05:27:28PM +0200, intrigeri wrote:
jon <j...@seniorblanco.com> wrote:
Venkman locks up when manually stepping through scripts.
Can this bug be reproduced using current Wheezy's xul-ext-venkman
0.9.89-1?
The question still stands (I’m not myself a venkman user).
Incidentally, I haven't looked at this in a very long time either. It
could already be working, and its possible also maybe the newer versions
of the native developer plugins in iceweasel *do* have step-through
debugging. They didn't when I originally opened this issue though.
Thanks for your answer, but you must reply to 626...@bugs.debian.org so
your input don’t get lost.
Can anyone comment on the native developer plugins in Iceweasel features?
Regards
David
I actually just tried it last night and found a step-through debugging
feature built-in, but was unable to figure out how (or if) it was
capable of loading a page and pausing the JavaScript by default, which
meant all the JavaScript was already executed by the time I could access
the "step over/step into" buttons making them ... as far as I could
tell, vestigial. Perhaps this is a separate bug I am having with the
current iceweasel in sid, or perhaps it is my user error, but without
the ability to halt the execution of the JavaScript immediately at page
load there is almost no practical use case for this tool. Venkman
allows for loading JavaScript without first automatically executing any
of it, allowing the *whole* execution to be stepped through from
immediately at page load to completion, and it provides a more complete
set of tools for examining object values during execution than this new
built-in debugger appears to have as well. Am I wrong? Am I merely not
using it right? Has Venkman's functionality completely been replaced
and I just can't see it, or am I actually just the only one who has
noticed/cared that it has not?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQEcBAEBCAAGBQJSOe76AAoJEAWMHPlE9r08Ts4H/0XZy3OOH2FoPAdwzLWxgZYH
PBTj+/XS/v0vgeuGdASoMjliJdnGVOKK3j+1gCYoOg9ge9Kp8q4TGyWf1rJ1nJum
7b+18rpKezEohQUZ5ML4d6Ze6UcuV9VyUosXt4LMuElDG7hMSI5TugRNcYJ8qDT7
IpjiqbqEfXN7XB6D2h35pnrF4eIkSuxHWi1ZKyXFeJgLb+Ju1zdnTTAHKCT/IH4m
cVNWu1Z9nV8DItxB3MX1XSSJVqmGKbkv5Lr2kz55e1OVC0dsXGFet5Rd2tVV2xxX
4nypf/F91PQQx5BeTiEL46Kyd2O2J36TrZmvrWaKLl0Tvw6QDLxRlaQ4a813mUQ=
=QN5g
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
