Pablo Galindo Salgado
Pablo Galindo Salgado
> Somebody from Apple needs to come here and confirm that this warning is a fluke. Otherwise, we have a problem 🙈 Yeah, we are unlikely to proceed with anything...
Unfortunately I don't feel comfortable landing this so late in the release cycle, specially so close to RC1 and given the current stability of 3.11 :( This will need to...
Oh interesting, can you confirm that changing the domain to memory makes the test fail?
Test only PRs are generally ok to backport 👍
In short, requesting the GIL or calling into GIL-requiring Python C-API calls like `PyGILState_GetThisThreadState` within a `malloc` call is incorrect because another thread may be joining the thread that calls...
This happens a lot if you are calling in any Python extension that goes into native code and this code spawns threads. Extensions may need to do these calls with...
> @pablogsal cc @erlend-aasland > > Is this patch will affect trampoline implementation? > It has potential to, specifically it may affect unwinders (including perf), debuggers and state inspection tools....
I'm also checking with the buildbot fleet.
From https://lore.kernel.org/linux-arm-kernel/[email protected]/t/ : > Perf report cannot produce callgraphs using dwarf on arm64 where pointer authentication is enabled. This is because libunwind and libdw cannot unmangle instruction pointers that have...
This makes `test_gdb` fail on aarch64 RHEL buildbots, so this more or less confirms that this messes up with debuggers as I suspected.