[02:52] *** [Coke] left
[04:48] *** [Coke] joined
[05:27] *** apogee_ntv left
[05:53] *** nine left
[05:53] *** nine joined
[08:10] *** ShimmerFairy left
[08:11] *** ShimmerFairy joined
[10:45] *** apogee_ntv joined
[14:27] *** riaty joined
[14:27] *** riaty left
[14:55] *** disbot1 joined
[16:53] <Geth> ¦ MoarVM/moar-rrdb-2: f0b60f9c7d | (Timo Paulssen)++ | tools/libmoar.so-gdb.py

[16:53] <Geth> ¦ MoarVM/moar-rrdb-2: gdb plugin: timeline command looks for invokes/returns in smaller area

[16:53] <Geth> ¦ MoarVM/moar-rrdb-2: 

[16:53] <Geth> ¦ MoarVM/moar-rrdb-2: Instead of trying to go to the beginning of the current event (which somehow

[16:53] <Geth> ¦ MoarVM/moar-rrdb-2: is a bit wonky regarding where you end up if you just "run event-number")

[16:53] <Geth> ¦ MoarVM/moar-rrdb-2: or running backwards (which is very slow) we seek-ticks (which is surprisingly

[16:53] <Geth> ¦ MoarVM/moar-rrdb-2: fast somehow?) in bigger and bigger steps backwards from our current position

[16:53] <Geth> ¦ MoarVM/moar-rrdb-2: and run forwards until the last starting position until we've gathered enough

[16:53] <Geth> ¦ MoarVM/moar-rrdb-2: <…commit message has 13 more lines…>

[16:53] <Geth> ¦ MoarVM/moar-rrdb-2: review: https://github.com/MoarVM/MoarVM/commit/f0b60f9c7d

[16:53] <Geth> ¦ MoarVM/moar-rrdb-2: c05d365d2c | (Timo Paulssen)++ | tools/libmoar.so-gdb.py

[16:53] <Geth> ¦ MoarVM/moar-rrdb-2: gdb plugin: rrdb: fix syntax in suggested command to load existing rrdb

[16:53] <Geth> ¦ MoarVM/moar-rrdb-2: review: https://github.com/MoarVM/MoarVM/commit/c05d365d2c

[16:53] <Geth> ¦ MoarVM/moar-rrdb-2: 7427d77e54 | (Timo Paulssen)++ | tools/libmoar.so-gdb.py

[16:53] <Geth> ¦ MoarVM/moar-rrdb-2: gdb plugin: refactor timeline / stack output

[16:53] <Geth> ¦ MoarVM/moar-rrdb-2: review: https://github.com/MoarVM/MoarVM/commit/7427d77e54