Skip to content

Conversation

@alehander92
Copy link
Member

@alehander92 alehander92 commented Oct 7, 2025

currently the feature depends on connecting with IPC/socket to a worker, built from some of our closed source code: currently only db-backend is open source, not rr-backend or the new rr worker code

(many things are currently custom there/configured only on my machine, so the build needs to be fixed if we merge something like this)

(more info in our private rr backend repo PR 17 )

@alehander92 alehander92 marked this pull request as draft October 7, 2025 17:22
@alehander92 alehander92 self-assigned this Oct 7, 2025
@alehander92 alehander92 added enhancement New feature or request refactor A system was refactored db-backend labels Oct 7, 2025
@alehander92 alehander92 force-pushed the feat-rr-with-db-backend branch 6 times, most recently from 6ac126f to 2d5f276 Compare October 13, 2025 19:15
@alehander92 alehander92 force-pushed the feat-rr-with-db-backend branch 3 times, most recently from c549472 to 67a6ec0 Compare October 21, 2025 16:26
@alehander92 alehander92 force-pushed the feat-rr-with-db-backend branch 3 times, most recently from 869c578 to e758084 Compare October 29, 2025 18:49
@alehander92 alehander92 force-pushed the feat-rr-with-db-backend branch 2 times, most recently from dcc446c to e2bed0a Compare November 5, 2025 11:31
there were problems with stdio, this is just ok for now
some help from Nikola for some bugs
i(alexander) wasn't sure if it can work well bidirectionally,
but it seems it's ok
loading locals still TODO in rr; overally not very tested in db
…ete generated test

tcp test by mistake committed before: generated with gemini/zed iirc: removing,
maybe if we add full tcp support we can add it

problem: dap backend server still seems to have an error, at least stdio one
works
TODO: a lot of things; is it ok to test like this a closed source part:
ct-rr-worker?
also, depends on many build artifacts that are not stable/ready for others
(lldbinit.py in workdir: src/db-backend; ct-rr-worker build)
also, a problem with socket in the end, non-critical
also depends on local `rr-trace` in src/db-backend: it can be recorded
from rust `rr_gdb.rs` from `codetracer-rr-backend`: TODO automate this for test?

currently ignored by default: run with `cargo test -- --ignored rr`
* testing:
  * add a simple test for it in rr_test
  * add a timeout for the rr test for now with the `ntest` crate
* impl:
  * start refactoring flow_preloader; not finished
… for location

for now working in simple cases for db-backend, and at least not crashing for
some for rr; but not yet a good example of working for rr;

a small fix that tries to repeat the function first/last info for each of the
lines in range in expr_loader; maybe we can instead check the region but for now
hopefully an ok fix

IMPORTANT: some problems overally: jumps and some flow in db-backend seem to be
broken
not sure why we seem to still receive additional stopped after maybe
complete-move/response, but it doesn't seem to be a problem
i forgot that now we mostly move with `self.replay`, so just changing the
handler step_id might not be enough

problem with iterate_asteroids flow remains
moved setBreakpoints logic to handler; implemented some of the methods
and placeholders for the others
…he newer value form

useful for rr: for now add some convert functions for compatibility;
maybe in the future try to replace the old `Value` with the newer versions
try with upstream `rr` in PATH and ct rr worker trying to use it:
but hanging; the test seems to be ok with the dev worker
building but not tested correctly: also more work! TODO
@alehander92 alehander92 force-pushed the feat-rr-with-db-backend branch from e2bed0a to f95979e Compare November 5, 2025 13:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

db-backend enhancement New feature or request refactor A system was refactored

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants