The Timelapse project is cool but this thread got derailed. We have a long
list of future improvements to make to rr, and improving support for JS
debugging is on that list.
The point of this thread is that if you're debugging intermittent test
failures and you don't need much JS debugging then yo
On 17/04/14 01:22, Kyle Huey wrote:
I definitely recall attending a brownbag presentation from a
researcher who had built a record and replay scheme for JS at the
office in MV sometime in the last few years.
- Kyle
That would be https://air.mozilla.org/timelapse/ .
A short video: https://www.y
On Tue, Apr 15, 2014 at 4:14 PM, Gijs Kruitbosch
wrote:
> On 16/04/2014 00:05, Robert O'Callahan wrote:
>>
>> We just released rr 1.2 and I think this would be a good time for people
>> to
>> try to use it for one of the tasks it was designed for: debugging
>> intermittent test failures.
>
>
> Thi
Building a debugger for a high-level language on top of a low-level
recording is unexplored territory but it's definitely possible and it would
have some nice features. However, you can't get much leverage from any
existing debugging support built into a VM.
We could build some JS debugging suppor
On Wed, Apr 16, 2014 at 7:14 AM, Till Schneidereit <
t...@tillschneidereit.net> wrote:
> On Wed, Apr 16, 2014 at 1:52 AM, Ehsan Akhgari wrote:
>
>> On 2014-04-15, 7:14 PM, Gijs Kruitbosch wrote:
>>
>>> On 16/04/2014 00:05, Robert O'Callahan wrote:
>>>
We just released rr 1.2 and I think this
On 04/15/2014 07:14 PM, Gijs Kruitbosch wrote:
1) Is anyone working on something similar that works for frontend code
(particularly, chrome JS)? I realize we have a JS debugger, but
sometimes activating the debugger at the wrong time makes the bug go
away, and then there's timing issues, and th
On Wed, Apr 16, 2014 at 11:14 PM, Till Schneidereit <
t...@tillschneidereit.net> wrote:
> At the JS work week in Toronto in late March, we discussed this.
> Unfortunately, that was one of the relatively few sessions for which no
> protocol exists. :(
>
> The gist of the results was that, sadly, th
On 16/04/2014 12:14, Till Schneidereit wrote:
On Wed, Apr 16, 2014 at 1:52 AM, Ehsan Akhgari wrote:
On 2014-04-15, 7:14 PM, Gijs Kruitbosch wrote:
On 16/04/2014 00:05, Robert O'Callahan wrote:
We just released rr 1.2 and I think this would be a good time for
people to
try to use it for one
On Wed, Apr 16, 2014 at 1:52 AM, Ehsan Akhgari wrote:
> On 2014-04-15, 7:14 PM, Gijs Kruitbosch wrote:
>
>> On 16/04/2014 00:05, Robert O'Callahan wrote:
>>
>>> We just released rr 1.2 and I think this would be a good time for
>>> people to
>>> try to use it for one of the tasks it was designed fo
On Wed, Apr 16, 2014 at 12:24 PM, Ted Mielczarek wrote:
> Do you have any idea on a timeframe for x86-64 support?
>
It's technically not that hard, but it's a reasonably large project so it's
not going to happen right away.
Rob
--
Jtehsauts tshaei dS,o n" Wohfy Mdaon yhoaus eanuttehrotraii
- Original Message -
> Do you have any idea on a timeframe for x86-64 support? I have a 64-bit
> Ubuntu install, and historically it's a bit of a pain to get 32-bit
> Firefox running. (Alternately, if someone wants to figure out
> instructions for getting a 32-bit Firefox built and running
On 4/15/2014 7:05 PM, Robert O'Callahan wrote:
>
> The steps to get started doing this are roughly as follows:
> 1) Install rr on a Westmere-or-later Linux system (or VM with performance
> counters virtualized), build 32-bit Firefox (opt or debug) and verify that
> recording Firefox works for you.
On Wed, Apr 16, 2014 at 11:14 AM, Gijs Kruitbosch
wrote:
> 1) Is anyone working on something similar that works for frontend code
> (particularly, chrome JS)? I realize we have a JS debugger, but sometimes
> activating the debugger at the wrong time makes the bug go away, and then
> there's timing
On Wed, Apr 16, 2014 at 11:05 AM, Robert O'Callahan wrote:
> 1) Install rr on a Westmere-or-later Linux system (or VM with performance
> counters virtualized), build 32-bit Firefox (opt or debug) and verify that
> recording Firefox works for you. If it doesn't, please file a github issue
> or chec
On 2014-04-15, 7:14 PM, Gijs Kruitbosch wrote:
On 16/04/2014 00:05, Robert O'Callahan wrote:
We just released rr 1.2 and I think this would be a good time for
people to
try to use it for one of the tasks it was designed for: debugging
intermittent test failures.
This is awesome! Three question
On Wed, Apr 16, 2014 at 11:05 AM, Robert O'Callahan wrote:
> 4) Create a script somewhere called rr-record that does "exec ~/rr/bin/rr
> record $*"
>
Sorry; this script, of course, needs to exec rr from wherever it was
installed.
Rob
--
Jtehsauts tshaei dS,o n" Wohfy Mdaon yhoaus eanuttehro
On 16/04/2014 00:05, Robert O'Callahan wrote:
We just released rr 1.2 and I think this would be a good time for people to
try to use it for one of the tasks it was designed for: debugging
intermittent test failures.
This is awesome! Three questions:
1) Is anyone working on something similar th
We just released rr 1.2 and I think this would be a good time for people to
try to use it for one of the tasks it was designed for: debugging
intermittent test failures.
Consult http://rr-project.org for more information, but the gist is this:
you can use rr to record the execution of Firefox test
18 matches
Mail list logo
