Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I've tried ChromeBug, it doesn't seem to work.</p> <p>With FireBug I have had the starting point of success by adding "debugger" to my GM code. This causes a breakpoint and I can inspect variables on the stack, but the right file is not shown so I can't step or anything.</p> <p>I have had the best success with FirebugMonkey (https:// addons.mozilla.org/en-US/firefox/addon/13623/), which I just got working to do basic debugging of GreaseMonkey scripts thanks to some explanation in a recent comment on the extension page by f0rsvinn. Here are the instructions I just posted at <a href="http://groups.google.com/group/greasemonkey-users/browse_thread/thread/994cfa58c79d222" rel="nofollow">http://groups.google.com/group/greasemonkey-users/browse_thread/thread/994cfa58c79d222</a>:</p> <p>It never occurred to me that the way it works is by creating its own sandbox around the script rather than using Greasemonkey's, you actually have to turn GM off. There are some GM aspect things that will not work though because the script really isn't in GreaseMonkey. As an example, GM_getValue returns undefined.</p> <p>Still, it works for basic debugging - and is way better than nothing.</p> <p>Usage steps are as follows:</p> <ol> <li>Install FireBug 1.5.4 (later versions do not seem to work)</li> <li>Install FireBugMonkey</li> <li>Use the Script Manager in FireBugMonkey to select the files you want to debug</li> <li>Disable GreaseMonkey (scripts will run inside FireBugMonkey, not</li> <li>GreaseMonkey)</li> <li>Enable FireBugMonkey</li> <li>Enable scripts in FireBug</li> </ol> <p>The scripts you added in the ScriptManager should be visible in the FireBug scripts list.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload