GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||
GeezerVison is showing github.com — gh-118518: Use the raw syscall directly for gettid by pablogsal · Pull Request #118592 · python/cpython Conversation
|
|
!buildbot AMD64 RHEL8 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
🤖 New build scheduled with the buildbot fleet by @pablogsal for commit a08d6b4 🤖 The command will test the builders whose names match following regular expression: The builders matched are:
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| ev.base.time_stamp = get_current_monotonic_ticks(); | ||
| ev.process_id = getpid(); | ||
| ev.thread_id = gettid(); | ||
| ev.thread_id = syscall(SYS_gettid); |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Perhaps it would make sense to leverage the existing thread API, e.g. PyThread_get_thread_native_id()?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I did that first but that has a check first for !initialized that calls PyThread_init_thread and that was causing problems when fork happens.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.