rr gdb session shows the current environment, not the environment of the recording
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
I was thinking that gdb's "show environment" would be a great way to see the HOSTNAME that a recording came from. No such luck, it just shows me the hostname that I'm replaying on.
Isn't that a bug? I.e. the intent of the time-travel debugging session is to accurately simulate debugging within the time and place the software was recorded, irrespective of where it's replayed...
To reproduce:
$ rr record ls
...
$ HOSTNAME=foobar rr replay
...
$ show environment
...
HOSTNAME=foobar
Expected: the real hostname above instead of "foobar".
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the rr record/replay path and the GDB show environment command described in the report. Reproduce with rr record ls followed by HOSTNAME=foobar rr replay, then trace where the environment is sourced. Done means show environment reports the recorded hostname rather than foobar.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100