Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RISC-V] test_gdb: AssertionError: 'Garbage-collecting' not found in 'Breakpoint 1 at 0x20f274 in test_gdb.test_backtrace #113083

Closed
furkanonder opened this issue Dec 14, 2023 · 1 comment
Labels
tests Tests in the Lib/test dir type-bug An unexpected behavior, bug, or error

Comments

@furkanonder
Copy link
Contributor

furkanonder commented Dec 14, 2023

Bug report

Bug description:

The same test case passes without a problem in a CPython build compiled with GCC.

Configuration:

./configure --with-pydebug --with-cxx-main=/usr/bin/clang++ CC=/usr/bin/clang

Test:

user@starfive:~/cpython$ ./python -m test test_gdb
Using random seed: 1502785800
0:00:00 load avg: 2.33 Run 5 tests sequentially
0:00:00 load avg: 2.33 [1/5] test_gdb.test_backtrace
test test_gdb.test_backtrace failed -- Traceback (most recent call last):
  File "/home/user/cpython/Lib/test/test_gdb/test_backtrace.py", line 103, in test_gc
    self.assertIn('Garbage-collecting', gdb_output)
    ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 'Garbage-collecting' not found in 'Breakpoint 1 at 0x20f274: file Python/bltinmodule.c, line 1261.\n[Thread debugging using libthread_db enabled]\nUsing host libthread_db library "/lib/riscv64-linux-gnu/libthread_db.so.1".\n\nBreakpoint 1, builtin_exec_impl (source=<optimized out>, globals=<optimized out>, locals=0x0, closure=<optimized out>, module=<optimized out>) at Python/bltinmodule.c:1261\n1261\t{\nBreakpoint 2 at 0x2aaad80394\n[Inferior 1 (process 117066) exited normally]\nUnable to locate python frame\n'

0:00:18 load avg: 1.95 [2/5/1] test_gdb.test_cfunction -- test_gdb.test_backtrace failed (1 failure)
0:00:21 load avg: 1.95 [3/5/1] test_gdb.test_cfunction_full
0:00:24 load avg: 1.88 [4/5/1] test_gdb.test_misc
0:01:18 load avg: 1.35 [5/5/1] test_gdb.test_pretty_print -- test_gdb.test_misc passed in 54.4 sec
value has been optimized out
Left operand of assignment is not an lvalue.
value has been optimized out
value has been optimized out
value has been optimized out
test test_gdb.test_pretty_print failed -- multiple errors occurred; run in verbose mode for details
test_gdb.test_pretty_print failed (1 error, 21 failures) in 1 min 23 sec

== Tests result: FAILURE ==

2 tests failed:
    test_gdb.test_backtrace test_gdb.test_pretty_print

3 tests OK.

Total duration: 2 min 41 sec
Total tests: run=39 failures=22 skipped=33
Total test files: run=5/5 failed=2
Result: FAILURE

Environment:

user@starfive:~/cpython$ uname -a
Linux starfive 5.15.0-starfive #1 SMP Fri Nov 24 07:22:28 UTC 2023 riscv64 GNU/Linux
user@starfive:~/cpython$ clang -v
Debian clang version 16.0.6 (19)
Target: riscv64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC installation: /usr/bin/../lib/gcc/riscv64-linux-gnu/12
Found candidate GCC installation: /usr/bin/../lib/gcc/riscv64-linux-gnu/13
Selected GCC installation: /usr/bin/../lib/gcc/riscv64-linux-gnu/13

CPython versions tested on:

CPython main branch

Operating systems tested on:

Other

@furkanonder furkanonder added type-bug An unexpected behavior, bug, or error tests Tests in the Lib/test dir labels Dec 14, 2023
@vstinner vstinner changed the title AssertionError: 'Garbage-collecting' not found in 'Breakpoint 1 at 0x20f274 in test_gdb.test_backtrace [RISC-V] [RISC-V] test_gdb: AssertionError: 'Garbage-collecting' not found in 'Breakpoint 1 at 0x20f274 in test_gdb.test_backtrace Sep 2, 2024
@furkanonder
Copy link
Contributor Author

Since the issue is no longer present in version 3.13, 3.12, and the main branch, I am closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tests Tests in the Lib/test dir type-bug An unexpected behavior, bug, or error
Projects
None yet
Development

No branches or pull requests

1 participant