Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Extension Debugging tools
17 views
Skip to first unread message
CheekySp
Mar 12, 2012, 3:06:42 PM3/12/12
to
What tools are you guys using for debugging extensions?
The reason I ask is this: I used Chromebug+ Firebug for some time and
it was quite handy, however Chromebug development had stopped and it
won't work on any FF since 5.0.
I've tried Venkman however cannot get it to work with extensions.
Any hints?
The reason I ask is this: I used Chromebug+ Firebug for some time and
it was quite handy, however Chromebug development had stopped and it
won't work on any FF since 5.0.
I've tried Venkman however cannot get it to work with extensions.
Any hints?
Gijs Kruitbosch
Mar 12, 2012, 5:18:28 PM3/12/12
to
as much as it does, anyway, it's not being actively developed)
~ Gijs
CheekySp
Mar 13, 2012, 3:59:06 AM3/13/12
to
On Mar 13, 3:18 am, Gijs Kruitbosch
I've tried starting Firefox with "-venkman" switch as suggested by
someone on the web, however only Venkman window opens - Firefox never
starts up and there's no way to launch it from Venkman itself. I can't
believe it's so complicated :-)
>
> Untick 'Exclude browser files' in the Debug menu, and Venkman should work (well,
> as much as it does, anyway, it's not being actively developed)
>
> ~ Gijs
Thanks Gijs, however it still does not show my extension files.
> Untick 'Exclude browser files' in the Debug menu, and Venkman should work (well,
> as much as it does, anyway, it's not being actively developed)
>
> ~ Gijs
I've tried starting Firefox with "-venkman" switch as suggested by
someone on the web, however only Venkman window opens - Firefox never
starts up and there's no way to launch it from Venkman itself. I can't
believe it's so complicated :-)
Gijs Kruitbosch
Mar 13, 2012, 6:46:56 AM3/13/12
to
suggestions:
You can run Firefox with both Venkman and a browser window by adding a
'-browser' switch as well (see firefox --help for more potentially useful options).
Regarding not seeing your code, I don't think using the commandline switch will
necessarily help, but have a read through:
http://www.gijsk.com/blog/2010/08/venkman-0-9-88-1/ (disclaimer: that's my blog,
and it's old).
The reason it's so complicated is that the architecture of Venkman is 10 years
old or so, and in the meantime JS engines, including Spidermonkey and its monkey
friends, have evolved. A lot. And Venkman (and the debugging API in
Spidermonkey) didn't really evolve nearly as aggressively. The API side of that
is currently being fixed, along with work on having a better user experience
when debugging websites (see
http://blog.astithas.com/2012/02/debugging-javascript.html ). To my knowledge,
nobody is working on making debugging chrome less painful (yet).
Hope that clarifies a bit...
Cheers,
Gijs
gNeandr
Mar 13, 2012, 8:28:37 AM3/13/12
to
I can support your question very much. Developing & debugging Mozilla
(FX,TB,SM,PB) based extensions isn't a fun these days. My experience
with ReminderFox development is quiet similar.
These days I'm using Venkman version 0.9.88.2. and Dom Inspector ..
because the Chromebug works anymore. Hard days, YES!!
If you use Venkman (VM), start FX (or TB) and manually start VM from
main menu. Normally, you will NOT see any extension specific functions
etc at that moment. Start/use your extension, after that you will see
the "used" functions with the "Loaded Scripts". Start to trace, set
break points etc.
Hope it helps ..
.. and if anybody has a better tracing/debugging tool/approach I'm hot
to follow that ;)
Günter
0 new messages