On Wednesday, January 4, 2012 3:43:23 PM UTC+1, Michael Braithwaite wrote:
>
> Hi,
>
> Not sure if this is a Firebug or Firefox issue.
>
> We have a NPAPI plugin which exposes JS objects and for some cases
> these use NPN_PluginThreadAsyncCall() etc to start another script
> executing. The scripts can be debugged with Firebug as normal however
> when debugging using Firefox 9 the NPN_PluginThreadAsyncCall() appears
> to carry on running even thought Firebug has halted another script
> resulting in other scripts being executed while stepping. I saw a bug
> on FF about needing to stop timers
> https://bugzilla.mozilla.org/show_bug.cgi?id=580880
> so I'm guessing this is another case that needs to block?
Yes this looks like another case that needs to block.
(perhaps JSD2 could solve this problem)
> Chrome/
> WebInspector works as expected.
>
> I wondered if there is some way to detect the script is paused, e.g. a
> hook that happens before/after Firebug breaks/resumes?
>
You should be able to register an event listener to Firebug.connection
object
Firebug.connection.addListener(listener);
Firebug.connection.removeListener(listener);
var MyListener =
{
onStop: function(context, frame, type,rv)
{
// debugger paused
},
onResume: function(context)
{
// debugger resumed
}
}
But I didn't test that.
Honza
> cheers,
>
> Michael
>
>
--
You received this message because you are subscribed to the Google
Groups "Firebug" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
https://groups.google.com/forum/#!forum/firebug
