![]() ![]() The nearest I got was the idea of method swizzling, but I don't think that's going to work for, say, queued NSOperation threads. Sometimes, I get another error, similar to the 'NULL new thread state' error: Fatal Python error: Couldnt create autoTLSkey mapping I guess that the reason is the same: memory allocation failed. Well I found out where the limitation came from, indeed the default thread stack size is set by the system is: stack size (kbytes, -s) 8192 I have wrote a simple C program to see what is the limit of the thread creation, and even if I create. ![]() I've investigated and sought various debugging methods but without success. Said differently: in low memory condition, creating a new thread may exit the whole Python process if a memory allocation fail. _block_global_6, _dispatch_call_block_and_release and so on). Is there a way of identifying where in the source-code a particular thread was spawned? And is there a way of determining to which NSOperationQueue an NSOperation belongs?įor example, I can see in the Debug Navigator (or by using LLDB's "thread backtrace" command) a thread's stacktrace, but the 'earliest' user code I can view is the overridden (NSOperation*) start method - stepping back earlier in the stack than that just shows the assembly instructions for the framework that invokes that method (e.g. QThread::start: Thread creation error: Resource temporarily unavailable. When running the code and debugging, I can see in Xcode's Debug Navigator the various threads that are running. I need to create such a plan in order to understand how the app works and what it's doing. I don't have access to a plan of the multithreaded architecture, that's to say a high-level design document of what is supposed to happen when. Important symptom - ldd myapp in the container returned 'ldd: error: you do not have read permission for myapp'. For more information, see the GitHub FAQs in the Python's Developer Guide. I have been asked to debug, and improve, a complex multithreaded app, written by someone I don't have access to, that uses concurrent queues (both GCD and NSOperationQueue). Issue 7544: Fatal error on thread creation in low memory condition - Python tracker Issue7544 This issue tracker has been migrated to GitHub, and is currently read-only.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |