Re: Debugger not stopping at hard breakpoint in xul javascript.

John J. Barton wrote:
> (I assume you are using venkman). I don't know what you mean by a "hard
> breakpoint".  Does the source have a dash '-' in front of the line you
> breakpoint? That indicates a line that venkman thinks is in the scripts
> line table.  If yes, then the script you breakpointed just isn't the
> script your extension is running: the browser isn't breakpointing
> because the code isn't running.  If no, then hmm, my guess would be the
> same.  From the debuggers point of view there isn't anything special 
> about scripts from extensions.

I meant a hard breakpoint by an actual breakpoint that is set and has a 
"B" in the source window.  i.e., not a future breakpoint with an "F".

The source lines do indeed have a "-" in front of the line I'm trying to 
set.

You may be right about the browser not running that code.  I don't see 
any other source files that match the name of my source files in my 
extension.  Is is possible they are somehow renamed in FireFox/Venkman? 
  The code is running.  I have a debug function dumping information to 
the console, and the exact places I'm trying to break at are printing 
debug information when I click or handle an event.

Thanks for your input.
Dennis