Error when recording: "The futex facility returned an unexpected error code."
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
I am running the debian binaries and master branch on my Ubuntu 22.04 x86_64 machine. I am getting this error upon upgrading to 5.6.0. I downgraded to 5.5.0 and it seems to be working.
According to the last comment in this issue it's to do with a mismatch between some libraries or glibc versions:
https://github.com/rr-debugger/rr/issues/2767
With version 5.6.0:
↳ rr record integration-service config.yaml
rr: Saving execution to trace directory `/home/russ/.local/share/rr/integration-service-4'.
[Integration Service][INFO] [is::sh::ROS2] Created node '/is_ros2_node_1804289383' with Domain ID: 0
The futex facility returned an unexpected error code.
zsh: IOT instruction rr record integration-service config.yaml
With version 5.5.0 (segfault is in my code):
↳ rr record integration-service config.yaml
rr: Saving execution to trace directory `/home/russ/.local/share/rr/integration-service-5'.
[Integration Service][INFO] [is::sh::ROS2] Created node '/is_ros2_node_1804289383' with Domain ID: 0
[Integration Service][INFO] [is::sh::ROS2] Configured!
zsh: segmentation fault rr record integration-service config.yaml
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 by reproducing rr record integration-service config.yaml on Ubuntu 22.04 x86_64 with rr 5.6.0, then compare the behavior with 5.5.0. Read the linked issue #2767 for the reported library or glibc mismatch context; done means the futex error no longer occurs with the 5.6.0 binaries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, debian, linux, ubuntu
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100