On Fri, Jan 17, 2014 at 10:44 PM, Ehsan Akhgari ehsan.akhg...@gmail.com wrote:
Our Firefox OS partners occasionally need to expose new APIs to Firefox OS
devices for things such as testing and diagnostics purposes.
What's that more concretely? Testing and diagnostics sounds like an
euphemism
Hi,
For those of you who are using LLDB -- either by choice, or against your
will after upgrading to OS X 10.9 -- I've added some Gecko-specific LLDB
functionality to an .lldbinit file in the tree. I've mainly started
with porting across the commands from the in-tree .gdbinit that were
This is fantastic, thank you so much!
a few months ago, I started looking into porting the pretty printers and
niceties for various SpiderMonkey things that live in js/src/gdb, but the
way much of this works is very different from gdb, so I didn't get too far
back them. This makes me want to pick
Hi Gio,
please read the previous messages in this thread: they contain answers to
all these questions. In fact, they're pretty much all answered right in the
first message[1].
[1]:
https://groups.google.com/d/msg/mozilla.dev.platform/o99wQZBjIJw/4eBoWbjEzjAJ
On Tue, Jan 21, 2014 at 7:02 AM,
It seems to me like the splitting algorithm for mochitests gives us
different chunking results on different platforms, see this test failure
for example:
https://tbpl.mozilla.org/?tree=Mozilla-Inboundrev=746018b05d67. Is this
expected? If not, is this easy to fix so that a given test always
On Jan 20, 2014, at 5:48 PM, Matt Woodrow m...@mozilla.com wrote:
Hi,
Currently in gecko we have code to determine if text being drawn into a
transparent surface has opaque content underneath it. In the case where it
doesn't we ask moz2d/cairo [1] to disable subpixel AA text rendering
On 1/21/2014 12:05 PM, Ehsan Akhgari wrote:
It seems to me like the splitting algorithm for mochitests gives us
different chunking results on different platforms, see this test failure
for example:
https://tbpl.mozilla.org/?tree=Mozilla-Inboundrev=746018b05d67. Is this
expected? If not, is
On 1/21/2014, 12:54 PM, Gregory Szorc wrote:
On 1/21/14, 9:05 AM, Ehsan Akhgari wrote:
It seems to me like the splitting algorithm for mochitests gives us
different chunking results on different platforms, see this test failure
for example:
Yeah. In general there are still some pain points using lldb, since a lot
of automation still assumes gdb (I'm looking at you, jit-tests). We're
going to have to use lldb going forward, so I think we should make it a
priority to improve the developer experience when using it.
bholley
On Tue,
On 1/21/14, 10:25 AM, Ehsan Akhgari wrote:
On 1/21/2014, 12:54 PM, Gregory Szorc wrote:
On 1/21/14, 9:05 AM, Ehsan Akhgari wrote:
It seems to me like the splitting algorithm for mochitests gives us
different chunking results on different platforms, see this test failure
for example:
The next MemShrink meeting will be brought to you by about:memory on B2G:
https://bugzilla.mozilla.org/show_bug.cgi?id=948774
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss how we measure
On 1/21/2014, 2:19 PM, Gregory Szorc wrote:
On 1/21/14, 10:25 AM, Ehsan Akhgari wrote:
On 1/21/2014, 12:54 PM, Gregory Szorc wrote:
On 1/21/14, 9:05 AM, Ehsan Akhgari wrote:
It seems to me like the splitting algorithm for mochitests gives us
different chunking results on different platforms,
On 1/21/2014, 4:27 AM, Henri Sivonen wrote:
On Fri, Jan 17, 2014 at 10:44 PM, Ehsan Akhgari ehsan.akhg...@gmail.com wrote:
Our Firefox OS partners occasionally need to expose new APIs to Firefox OS
devices for things such as testing and diagnostics purposes.
What's that more concretely?
Really nice Cameron, thanks for doing this!
Now if only I could get LLDB to work with GUD in emacs. If anyone has managed
that, I'd love to hear about it. There was some elisp in the LLDB repo at one
time but last I checked it had been removed and the last version that existed
didn't work with
14 matches
Mail list logo
