466121 - Debugger virtually unusable for breaking on errors/exceptions at debugger startup

Status: RESOLVED INCOMPLETE

(Other Applications Graveyard :: Venkman JS Debugger, defect)

Description

[mavigozler]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4
Build Identifier: Venkman version 0.9.87.4

There seems to be a file  'XPCSafeJSObjectWrapper.cpp' creating an impossible problem in using Venkman.  At Venkman startup it appears.  When reloading a page it appears, with the error always at line 445.  One has to hit the Continue button a half dozen times to get out of a debug session.  Selecting the file and telling it NOT to debug Contained Functions does not work.  The ONLY was to use Venkman is to set for ignoring errors and exceptions and using breakpoints.  The continuoulsy cycling report is show below.  By the way:  do a search on the partial string 'XPCSafe' and you will see about 7 other reports for different products where this line and this file are causing problems.


============
Continuing from error handler.
Warning ``reference to undefined property this[arguments[0]]'' [-s] in file ``XPCSafeJSObjectWrapper.cpp'', line 445, character 0.
Stopped for error handler.
#0: function anonymous() in <XPCSafeJSObjectWrapper.cpp> line 445
Error loading URL <XPCSafeJSObjectWrapper.cpp>: [Exception... "Component returned failure code: 0x804b000a (NS_ERROR_MALFORMED_URI) [nsIIOService.newChannel]" nsresult: "0x804b000a (NS_ERROR_MALFORMED_URI)" location: "JS frame :: chrome://venkman/content/venkman-url-loader.js :: _getChannelForURL :: line 54" data: no].
Error loading URL <XPCSafeJSObjectWrapper.cpp>: [Exception... "Component returned failure code: 0x804b000a (NS_ERROR_MALFORMED_URI) [nsIIOService.newChannel]" nsresult: "0x804b000a (NS_ERROR_MALFORMED_URI)" location: "JS frame :: chrome://venkman/content/venkman-url-loader.js :: _getChannelForURL :: line 54" data: no].
Error loading URL <XPCSafeJSObjectWrapper.cpp>: 2147500037.
================


Reproducible: Always

Steps to Reproduce:
1a. Start Venkman
1b. Optionally, re-load a page even after Venkman has been released from any debug session
Actual Results:  
Results are described as in details above:  the persistent breaking at this line 445 of the cpp file.

Expected Results:  
Venkman should ACTUALLY be set up or in a mode in which the USER specifies which files (HTML, JS, etc) and even functions are to be enabled for debugger control on the occurrence of exceptions and errors.  The 'Exclude Browser Files' option has proved ENTIRELY unuseful.  Consider this to be a requested feature change.

Comment 1

[BMO Automation]

Component is obsolete so resolving bugs as INCOMPLETE