327830 - "Error: console.commandManager has no properties"

Status: RESOLVED INVALID

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

Description

[JF Mertens]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/417.9 (KHTML, like Gecko) Safari/417.8
Build Identifier: seamonkey-1.0 built_from_src

When opening Tools/Web/JavaScript Debugger :
Error: MSG_ALERT is not defined
Source File: chrome://venkman/content/venkman-utils.js
Line: 248

and the debugger window is unusable

Reproducible: Always

Steps to Reproduce:
1.Build probably irrelevant, if not :
2.ConfigureParams: --enable-xft --disable-freetype2 --enable-calendar
--enable-optimize="-O3 -fstrict-aliasing" --disable-debug
--enable-application=suite --enable-macos-target=10.4 --enable-prebinding
--enable-default-toolkit=gtk2 --with-pthreads
--with-default-mozilla-five-home=%p/lib/%N --mandir=%p/share/man --enable-strip
--enable-extensions=all --enable-image-decoders=all --enable-ldap-experimental
--enable-xpctools --enable-necko-protocols=all --enable-efence
--enable-native-uconv --enable-ctl --enable-xinerama --with-system-mng
--with-system-jpeg --with-system-png --with-system-zlib --enable-postscript
--enable-ipv6 --enable-tests --with-x --enable-canvas --with-qtdir=%p
--enable-pango --enable-svg --enable-update-packaging --enable-storage
--enable-system-cairo --enable-profilesharing

3.For identical setup, grab my .info and .patch files from my experimental
dir:
http://cvs.sourceforge.net/viewcvs.py/fink/experimental/jfmertens/crypto/finkinfo/
and 'fink install seamonkey'


Actual Results:  
cf supra

Expected Results:  
-

The JavaScript debugger is broken with this.
Hence severity 'major'

Comment 1

[timeless]

um the contents of this are bug 327827, but the summary is a different problem.

Comment 2

[JF Mertens]

Sorry _ copied the wrong error msg.
For this bug, it is :

Error: console.commandManager has no properties
Source File: chrome://venkman/content/venkman-static.js
Line: 214

Comment 3

[James Ross]

I suggest you fix your build configuration problem, as mentioned in the resolution of bug 327827, and see if this still occurs. I bet it doesn't.

Comment 4

[JF Mertens]

Bug disappeared with
https://bugzilla.mozilla.org/show_bug.cgi?id=327835#10

JFm

Comment 5

[James Ross]

Resolving per other bugs -> invalid build config.