<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel about="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger">
    <title>gmane.comp.mozilla.devel.jsdebugger</title>
    <link>http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1193"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1192"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1191"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1190"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1189"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1188"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1187"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1185"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1184"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1183"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1182"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1181"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1180"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1179"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1178"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1177"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1176"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1175"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1174"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1173"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1193">
    <title>Re: test suite for jsd?</title>
    <link>http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1193</link>
    <description>
I believe there aren't. Be Bold! :-)
~ Gijs
</description>
    <dc:creator>Gijs Kruitbosch</dc:creator>
    <dc:date>2008-11-02T22:27:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1192">
    <title>test suite for jsd?</title>
    <link>http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1192</link>
    <description>Are there tests for the 'jsd' layer of the debugger api? If so where are 
they hiding? Thanks, John.
</description>
    <dc:creator>John J. Barton</dc:creator>
    <dc:date>2008-11-02T17:27:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1191">
    <title>Debugging stand-alone JS apps</title>
    <link>http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1191</link>
    <description>Hello,

There are several Eclipse JS debuggers around (e.g. in the Eclipse ATF
project) which use the jsdIDebuggerService interface, but they all
require XPCOM and run the debugger inside the Mozilla framework.

Since Spidermonkey is able to run without the Mozilla framework too, I
was wondering if it would be feasible to debug a JS application that
runs from a simple Linux shell?

Best regards,
Harald
</description>
    <dc:creator>Harald Krapfenbauer</dc:creator>
    <dc:date>2008-10-29T14:39:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1190">
    <title>interactive session</title>
    <link>http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1190</link>
    <description>I can't type anything into the interactive session, its as though the
keyboard is disabled anyone got any ideas or is it a bug, am using
running Venkman version 0.9.87.4 with Firefox 3.0.3
</description>
    <dc:creator>rnettle</dc:creator>
    <dc:date>2008-10-27T22:51:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1189">
    <title>Re: Firebug internals discussion?</title>
    <link>http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1189</link>
    <description>
http://groups.google.com/group/firebug


The signal to noise ratio on this group is high: mostly my posts and spam.


My proposal is to discuss 'jsd' and internal aspects of firebug. Of 
course others may choose to bring up the topics you suggest.


Three people from Mozilla work on Firebug.


The group here is mozilla.dev.apps.js-debugger, not .venkman.
</description>
    <dc:creator>John J. Barton</dc:creator>
    <dc:date>2008-09-30T04:18:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1188">
    <title>Re: Firebug internals discussion?</title>
    <link>http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1188</link>
    <description>On 05.08.2008 03:27 John J. Barton wrote


Yes, I would. Simply, because it should be possible to ask the admins to
create a 'mozilla.apps.firebug' group. That way one can safley assume,
that the messages one wants to browse belong to the software s/he is
using. We get overdrawn by information these days, it would be nice to
have some pre-filtering by keeping newsgroups at a low signal-to-noise
ratio.

Imagine topics like these:

- Can't get things to work!
- Debugging stops halfway in my code and hangs.
- Please help a newbie
- etc.

So our good reader opens these, reads into it, just to realize, that it
was about Venkman and not about Firebug (or vice versa). As it is,
Venkman still seems to be the semi-official js-debugger for Mozilla
code, so this group should stay for Venkman.

If any of the admins in responsibility are reading this, may I kindly
ask you to think about a 'mozilla.apps.firebug' group, since I would
like that one, too. I would appreciate that.

</description>
    <dc:creator>Andreas M</dc:creator>
    <dc:date>2008-09-29T21:50:53</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1187">
    <title>jsdIStackFrame scope jsParent</title>
    <link>http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1187</link>
    <description>A Firebug user just told me about "jsParent". This is a property of 
jsdIValue objects and it turns out that if the jsdIValue object is 
jsdIStackFrame.scope, then the jsParent is a link to the scope chain for 
the function on the stack.

Is there any way to get this scope chain from a jsdIScript object? Its a 
property of the function not the stack correct?

jjb
</description>
    <dc:creator>John J. Barton</dc:creator>
    <dc:date>2008-09-16T05:35:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1185">
    <title>isLineExecutable() very slow.</title>
    <link>http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1185</link>
    <description>Just a little tidbit from Firebug experience:

jsdIScript
http://www.xulplanet.com/references/xpcomref/ifaces/jsdIScript.html
has a method,
PRBool isLineExecutable ( PRUint32 line , PRUint32 pcmap )

Based on some very informal measurements I found that it takes about 1ms 
per line to call this method. When you apply that to 40k lines, not much 
goes on for while.

I don't know if this is intrinsic or just because of crossing in and out 
of C++ but it would be good to understand so we can create a faster next 
gen API.  For example we could replace this with

Array&lt;int&gt; executableLines(pcmap);

for most applications.

jjb
</description>
    <dc:creator>John J. Barton</dc:creator>
    <dc:date>2008-08-20T03:20:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1184">
    <title>Proposed changes to jsdIDebuggerService and friends</title>
    <link>http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1184</link>
    <description>Please take a look at
Modernize jsdIDebuggerService
https://bugzilla.mozilla.org/show_bug.cgi?id=449452
for links to several bug reports outlining improvements in jsd.

Of the possible ways to proceed, I am inclined to push for

Bug 379410 – debugger script detection using parent JSScript

or if this is too hard, then a limited version of

Bug 449454 – [jsd] Add frame argument to every jsd callback, eg 
jsdIScriptHook

John.
</description>
    <dc:creator>John J. Barton</dc:creator>
    <dc:date>2008-08-15T16:56:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1183">
    <title>Re: Firebug internals discussion?</title>
    <link>http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1183</link>
    <description>
Richard, might I ask what the objection is?

</description>
    <dc:creator>Justin Wood (Callek</dc:creator>
    <dc:date>2008-08-13T03:02:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1182">
    <title>Re: Firebug internals discussion?</title>
    <link>http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1182</link>
    <description>
Yes.

Richard

</description>
    <dc:creator>Richard Kramer</dc:creator>
    <dc:date>2008-08-12T13:39:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1181">
    <title>Re: Firebug internals discussion?</title>
    <link>http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1181</link>
    <description>
Given that this is m.d.a.js-debugger and not .venkman sure, it fits.

And furthermore as a user of both venkman and firebug I do prefer 
firebug of the two anyway, so the conversations will likely be enjoyable.

</description>
    <dc:creator>Justin Wood (Callek</dc:creator>
    <dc:date>2008-08-08T19:53:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1180">
    <title>Re: Firebug internals discussion?</title>
    <link>http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1180</link>
    <description>I would find it quite informative, please do.

On Mon, Aug 4, 2008 at 6:27 PM, John J. Barton &lt;johnjbarton&lt; at &gt;johnjbarton.com&gt;
wrote:

</description>
    <dc:creator>Wink Saville</dc:creator>
    <dc:date>2008-08-05T03:05:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1179">
    <title>Firebug internals discussion?</title>
    <link>http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1179</link>
    <description>Would the readers of this newsgroup object if we started discussing 
Firebug internal code here?

John.
</description>
    <dc:creator>John J. Barton</dc:creator>
    <dc:date>2008-08-05T01:27:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1178">
    <title>Re: Seamonkey 1.1.9 gets glacially slow after opening JS debugger</title>
    <link>http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1178</link>
    <description>On Thu, 26 Jun 2008 06:12:00 UTC in mozilla.dev.ports.os2, Peter Weilbacher 
&lt;newsspam&lt; at &gt;weilbacher.org&gt; wrote:


The behaviour stopped after a stop/start of Seamonkey and is now back to normal.
I'm reluctant to try it again because I've only just got my 11 tabs back open  
:-)


</description>
    <dc:creator>Trevor Hemsley</dc:creator>
    <dc:date>2008-06-26T17:44:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1177">
    <title>Re: Seamonkey 1.1.9 gets glacially slow after opening JS debugger</title>
    <link>http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1177</link>
    <description>
Hmm, it doesn't happen to me. I take it that you have tried to at least
restart SeaMonkey afterwards (and perhaps also reboot the system)?
I have no idea what could be causing either the initial delay when
starting the JS Debugger nor the subsequent slowness when loading pages.
AFAIK that tool doesn't have platform specific parts, so this might not
be tied to OS/2.

I'm cross-posting this to mozilla.dev.apps.js-debugger to get input from
people who actually know that tool.
</description>
    <dc:creator>Peter Weilbacher</dc:creator>
    <dc:date>2008-06-26T06:12:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1176">
    <title>How to open Venkman with a given file?</title>
    <link>http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1176</link>
    <description>Is it possible to programatically open Venkman with specified file
(chrome
url) opened by default, which is also automatically scrolled to a
given line?
Honza
</description>
    <dc:creator>Jan Odvarko</dc:creator>
    <dc:date>2008-06-18T20:05:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1175">
    <title>Re: jsdIFilter?</title>
    <link>http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1175</link>
    <description>
Thanks for your information. Unfortunately the only case I really need 
is scriptHook :-(.  The big overhead in Firebug is caused because the 
only way to sort out scripts is to have a stack and scriptHooks do not 
have a stack. So I have to take the scriptHook and set a breakpoint to 
get a stack.  I thought I could pay back some of the overhead if I could 
filter scriptHook calls to focus only on the ones that need processing.

John.
</description>
    <dc:creator>John J. Barton</dc:creator>
    <dc:date>2008-06-11T20:04:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1174">
    <title>Re: jsdIFilter?</title>
    <link>http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1174</link>
    <description>"John J. Barton" &lt;johnjbarton&lt; at &gt;johnjbarton.com&gt; wrote in message 
news:3uCdncXf_rue-NLVnZ2dnUVZ_rrinZ2d&lt; at &gt;mozilla.org...

except scriptHook. Venkman has a mini-example/test in 
http://mxr.mozilla.org/seamonkey/ident?i=cmdTestFilters. No guarantees on 
its stability, though, as I don't know of anything that actually uses it 
(besides that mini-test in Venkman).

Would be great if you can report back on if it works, doesn't work or takes 
down the world in a ball of fire. ;)

</description>
    <dc:creator>James Ross</dc:creator>
    <dc:date>2008-06-11T17:11:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1173">
    <title>jsdIFilter?</title>
    <link>http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1173</link>
    <description>Does anyone know if jsdIFilter works?  I guess I could try it, seems 
like a good thing if it worked...John.
</description>
    <dc:creator>John J. Barton</dc:creator>
    <dc:date>2008-06-11T05:45:53</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1172">
    <title>Re: Venkman in FireFox 3 (RC1)</title>
    <link>http://permalink.gmane.org/gmane.comp.mozilla.devel.jsdebugger/1172</link>
    <description>

https://bugzilla.mozilla.org/show_bug.cgi?id=428848

There's a working XPI on that bug.

~ Gijs
</description>
    <dc:creator>Gijs Kruitbosch</dc:creator>
    <dc:date>2008-05-25T19:10:17</dc:date>
  </item>
  <textinput about="http://search.gmane.org/?group=$group=gmane.comp.mozilla.devel.jsdebugger">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.mozilla.devel.jsdebugger</link>
  </textinput>
</rdf:RDF>
