Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

test_tracemalloc_track_race segfault on buildbot #143143

Open
Labels
testsTests in the Lib/test dirtype-crashA hard crash of the interpreter, possibly with a core dump
@colesbury

Description

@colesbury

Crash report

Seen on the ARM Raspbian 3.x buildbot, but I suspect it's not Raspbian specific:

https://buildbot.python.org/#/builders/424/builds/12446/steps/6/logs/stdio

0:02:36 load avg: 3.51 [177/497/1] test_tracemalloc worker non-zero exit code (Exit code -11 (SIGSEGV))test_late_untrack (test.test_tracemalloc.TestCAPI.test_late_untrack) ... oktest_stop_track (test.test_tracemalloc.TestCAPI.test_stop_track) ... oktest_stop_untrack (test.test_tracemalloc.TestCAPI.test_stop_untrack) ... oktest_tracemalloc_track_race (test.test_tracemalloc.TestCAPI.test_tracemalloc_track_race) ... Fatal Python error: Segmentation faultThread 0xf4afe400 [python] (most recent call first):Thread 0xf52ff400 [python] (most recent call first):  <freed thread state><freed thread state>Current thread's C stack trace (most recent call first):  <system returned no stack trace>Extension modules: math.integer, _testcapi, _testinternalcapi (total: 3)

Metadata

Metadata

Assignees

No one assigned

    Labels

    testsTests in the Lib/test dirtype-crashA hard crash of the interpreter, possibly with a core dump

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2026 Movatter.jp