15:27:37Josh_2anyone know if there is a library for the double ratchet algorithm described here https://signal.org/docs/specifications/doubleratchet/ ?
15:28:30ldbpaule32: assuming you want the algorithom in CL since you're asking question in #lisp
21:10:57drmeisterHey folks - I dunno how many of you do low level debugging with gdb or lldb.
21:11:14drmeisterBut if you do - you should check out the "Undo" time traveling debugger.
21:11:29drmeisterI've been using an evaluation copy for the last couple of days and it is amazing.
21:12:08drmeisterIt records the state of every instruction from when you connect to the process to a break-point. Then you can backup and examine registers.
21:12:43drmeisterHere I'm using it to debug a tricky problem in clasp's Common Lisp compiler.
21:28:03p_ldrmeister: yeah, though now I checked mostly in "professional services", so I guess custom patches for clients ;)
21:28:38p_lnice integration with source listing you have, never seen it work with other debuggers when it comes to lisp
21:29:33drmeisterYeah - we've been adding DWARF generation to clasp. We have a bit more work to do with inlined code. We have the inlinedAt chain - but we aren't generating the appropriate DWARF with it yet.
21:29:49drmeisterudb makes it easier to figure out where the holes in the DWARF coverage are.
21:30:47drmeisterI also wrote a python extension that works with gdb and lldb and lets you examine lisp objects from the outside using the gdb/lldb debugger.
21:31:03Faredrmeister, using Python is its own punishment.
21:34:00drmeisterAnyway - I have bigger fish to fry. I knocked the Python extension out in a couple of days and made it portable so that it works from lldb and gdb.
21:34:32drmeisterAaand with gdb I made it work with Python 3.7 and Python 2.7 (udb uses gdb8 and for some reason they use Python 2.7). Hi ho.