mozjs.dll!js::jit::BaselineScript::icEntryFromPCOffset(unsigned int
pcOffset) Line 553 C++
mozjs.dll!js::jit::DebugModeOSRVolatileStub::invalid() Line 56 C++
mozjs.dll!js::jit::DoGetElemFallback(JSContext * cx,
js::jit::BaselineFrame * frame, js::jit::ICGetElem_Fallback * stub_,
JS::Handle lh
Not sure how this works in Visual Studio, but check out:
http://www-archive.mozilla.org/scriptable/javascript-stack-dumper.html
In gdb you can do "call DumpJSStack()"
Philipp
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mo
This has now been merged to central. I've update the docs at:
https://developer.mozilla.org/en-US/docs/Mochitest
https://developer.mozilla.org/en-US/Firefox_OS/Automated_testing/Mochitests
In most cases just running |mach mochitest path/to/test/or/dir| will do
what you want. But if for some reaso
On 6/1/2015 2:53 AM, Philipp Kewisch wrote:
Not sure how this works in Visual Studio, but check out:
http://www-archive.mozilla.org/scriptable/javascript-stack-dumper.html
In gdb you can do "call DumpJSStack()"
Philipp
Here's what I do.
After your C++ breakpoint is hit, in Visual Studio do
On 01/06/2015 12:18, glob wrote:
> this started happening via
> https://bugzilla.mozilla.org/show_bug.cgi?id=972040
>
> please file a bug and we'll apply per-product filtering -- currently
> it'll be set on any product that has that flag.
I have filed https://bugzilla.mozilla.org/show_bug.cgi?i
On Thursday, 28 May 2015 08:09:55 UTC+5:30, Mike Hommey wrote:
> On Wed, May 27, 2015 at 11:38:30AM -0700, Meenakshi Shankar wrote:
> > Hi,
> >
> > We are using Firefox SDKS for our FF extension. The libs generated
> > after compiling Firefox 39 beta 1 source (using start-shell-msvc2013)
> > did
On Mon, Jun 01, 2015 at 12:51:23PM -0700, Meenakshi Shankar wrote:
> On Thursday, 28 May 2015 08:09:55 UTC+5:30, Mike Hommey wrote:
> > On Wed, May 27, 2015 at 11:38:30AM -0700, Meenakshi Shankar wrote:
> > > Hi,
> > >
> > > We are using Firefox SDKS for our FF extension. The libs generated
> > >
tl;dr - PR_LOG* are deprecated. Use MOZ_LOG* instead.
As part of the effort to improving logging in gecko we've started a transition
to using a MOZ prefix and a new set of log levels [1]. I've just landed these
changes on mozilla-inbound, if they stick this means you should no longer use
PR_LOG
On Sun, May 31, 2015 at 5:09 AM, Jonas Sicking wrote:
> We should use whatever formats people are using to mark up pages. If that is
> microdata we should use that. If it's RDF we should use that. If its JSONLD
> we should use that.
>
> The API that is used to extract the data is irrelevant. That
Benjamin,
Le 30 mai 2015 à 21:35, Benjamin Francis a écrit :
> But Microdata is only one of the formats widely used on the web today. I'd
> like to see some evidence-based discussion on which format(s) we should
> support to get the most possible value out of what already exists on the
> web. The
We enabled native copy-to-clipboard on github.com today for Firefox Nightly
visitors. The copy buttons no longer use a Flash widget in Nightly or Chrome!
Thanks so much for working on this, Ehsan.
David
On Wednesday, May 6, 2015 at 7:42:23 PM UTC-6, Ehsan Akhgari wrote:
> On 2015-05-06 2:51 PM
On Mon, Jun 1, 2015 at 4:31 PM, Anne van Kesteren wrote:
> On Sun, May 31, 2015 at 5:09 AM, Jonas Sicking wrote:
>> We should use whatever formats people are using to mark up pages. If that is
>> microdata we should use that. If it's RDF we should use that. If its JSONLD
>> we should use that.
>>
On June 1, 2015 at 17:34:48 , Jonas Sicking (jo...@sicking.cc) wrote:
> I think we're already talking about reverse-engineering what search
> engines and twitter/facebook/etc do.
>
> But I'm still all for proper standardization. Including driving
> towards good technical solutions.
Yup. We’re rea
13 matches
Mail list logo
