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've done a little more experimentation with the location that I set 
breakpoints at.  I found that if I set a breakpoint in a function call, 
having done no other breakpoints yet that the code stops for debugging. 
  If I set a breakpoint in an event handler that is called by adding the 
function to an event with "addEventListener", that the breakpoint is not 
called.  Furthermore, once I've tried that, the other breakpoints no 
longer work.  If I restart FireFox, the 1st type of breakpoints can be 
called again but I tried the process a couple times and got the same 
result each time.

Is there some special circumstance that deals with breakpoints inside of 
event handler code?

Thanks
Dennis