Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Possible issue with running rr with newer kernel, Debian 7.1.3-1~bpo13+1.

Aperta
  • Qualcosa non va?
#4,093 6 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 3 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
cpp, debian, linux
Ambito
operating-systems, reverse-engineering, testing-qa

Direzione di ricerca

Reproduce the failure with ctest --tests-regex '^ptrace_breakpoint$' and compare the Debian 13 stock and backports kernels. Start with src/test/ptrace_breakpoint.c and src/test/util.sh, using the reported pwrite errno and the ptrace_breakpoint, jit_proc_mem, and record_replay tests as evidence. Done means the affected tests pass on the newer kernel or the incompatibility is clearly characterized.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Trying to run the tests with current git @ 5c202cd8cb6 I found following started to fail.

ptrace_breakpoint
jit_proc_mem
record_replay

Going back to the commit @ a009e7e738, where these tests were working, unfortunately showed today the same issue.
The system is a Debian 13 Trixie with a 7.1.3-1~bpo13+1 kernel from backports.

Last month when above tests were running fine @ a009e7e738 I was running a 7.0.13-1~bpo13+1 kernel.

A test inside a minimal Debian 13 Trixie VM with stock kernel 6.12.101+deb13 showed the test "ptrace_breakpoint" working,
booting the exact same VM also with the backports kernel 7.1.3-1~bpo13+1 shows also the test failure @ a009e7e738, see below details.

Therefore my assumption this may be an issue when running a kernel 7.1.

Anyone else also seeing this issue?

benutzer@debian:.../obj$ ctest -j1 --verbose --tests-regex '^ptrace_breakpoint$'
UpdateCTestConfiguration  from :.../obj/DartConfiguration.tcl
UpdateCTestConfiguration  from :.../obj/DartConfiguration.tcl
Test project .../obj
Constructing a list of tests
Done constructing a list of tests
Updating test list for fixtures
Added 0 tests to meet fixture requirements
Checking test dependency graph...
Checking test dependency graph end
test 585
    Start 585: ptrace_breakpoint

585: Test command: /usr/bin/bash "source_dir/src/test/basic_test.run" "ptrace_breakpoint" "" "bin_dir" "120"
585: Working Directory: .../obj
585: Test timeout computed to be: 10000000
585: source_dir/src/test/util.sh: line 284:  1220 Aborted                 _RR_TRACE_DIR="$workdir" test-monitor $TIMEOUT record.err $RR_EXE $GLOBAL_OPTIONS record --bind-to-cpu=any $LIB_ARG $RECORD_ARGS "$exe" $exeargs > record.out 2> record.err
585: Test 'ptrace_breakpoint' FAILED: : token 'EXIT-SUCCESS' not in record.out:
585: --------------------------------------------------
585: FAILED at src/test/ptrace_breakpoint.c:47: !(bkpt_size == pwrite(mem_fd, breakpoint_instruction, bkpt_size, (uintptr_t)breakpoint)) errno:5 (Input/output error)
585: --------------------------------------------------
585: Test ptrace_breakpoint failed, leaving behind /tmp/rr-test-ptrace_breakpoint-u7Nakxqgw
585: To replay the failed test, run
585:   _RR_TRACE_DIR=/tmp/rr-test-ptrace_breakpoint-u7Nakxqgw rr replay
1/1 Test #585: ptrace_breakpoint ................***Failed  Error regular expression found in output. Regex=[FAILED]  0.21 sec

0% tests passed, 1 tests failed out of 1

Total Test time (real) =   0.33 sec

The following tests FAILED:
        585 - ptrace_breakpoint (Failed)
Errors while running CTest
Output from these tests are in: .../obj/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.
benutzer@debian:.../obj$
Lingua principale
C++
Stelle
10.7k
Fork
665
Merge medio
2g 7h
PR unite (30g)
3

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di rr-debugger/rr

Tutte le issue di rr-debugger/rr

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.