Hi John,
For some reason my response keeps not appearing here on:
http://groups.google.com/group/mozilla.dev.apps.js-debugger/browse_thread/thread/8e5ef196cd5e5746/9333c2826c02439a#9333c2826c02439a
The gist is that I tried what you suggested, still didn't solve my
problem, so I downloaded Mozilla 1.7.something for OS X, and it's
embedded debugger looks just like Venkman and works correctly on my
platform. Still not ideal, but at least I have a dev environment at
home now (work is WinXP and FF+Venkman works fine).
thanks
Chad
On Mar 8, 8:58 pm, "John J. Barton" <[email protected]>
wrote:
> James Ross wrote:
> > [email protected] wrote:
> >> No, still the same popup x-jsd error. I do notice that the interactive
> >> session displays the code surrounding 'debugger' when that gets hit in
> >> execution, but in order to set my own breakpoints, I need to be able
> >> to see the sourcecode in the sourcecode window eventually..
>
> > Indeed, but that's not exactly Venkman's fault - Venkman actually works
> > fine for me in Firefox 2 and trunk (to be 3). The source view is a page
> > loaded via an x-jsd URL - by far the best way to do it.
>
> > You'll really have to investigate what your Firefox has screwed up
> > yourself, but it sounds very much like Firefox is ignoring the
> > "venkman-service.js" file, which is where the x-jsd protocol is defined.
>
> Chad, if James is right you might try exiting FF then deleting xpti.dat
> and compreg.dat from your extensions directory. FF rebuilds them next
> you start.
> John.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.