android Thread class
system/core/libutils/include/utils/Thread.h
system/core/libutils/Threads.cpp
status_t Thread::run(const char* name, int32_t priority, size_t stack) 665{ 666 LOG_ALWAYS_FATAL_IF(name == nullptr, "thread name not provided to Thread::run"); 667 668 Mutex::Autolock _l(mLock); 669 670 if (mRunning) { 671 // thread already started 672 return INVALID_OPERATION; 673 } 674 675 // reset status and exitPending to their default value, so we can 676 // try again after an error happened (either below, or in readyToRun()) 677 mStatus = OK; 678 mExitPending = false; 679 mThread = thread_id_t(-1); 680 681 // hold a strong reference on ourself 682 mHoldSelf = this; 683 684 mRunning = true; 685 686 bool res; 687 if (mCanCallJava) { 688 res = createThreadEtc(_threadLoop, 689 this, name, priority, stack, &mThread); 690 } else { 691 res = androidCreateRawThreadEtc(_threadLoop, 692 this, name, priority, stack, &mThread); 693 } 694 695 if (res == false) { 696 mStatus = UNKNOWN_ERROR; // something happened! 697 mRunning = false; 698 mThread = thread_id_t(-1); 699 mHoldSelf.clear(); // "this" may have gone away after this. 700 701 return UNKNOWN_ERROR; 702 } 703 704 // Do not refer to mStatus here: The thread is already running (may, in fact 705 // already have exited with a valid mStatus result). The OK indication 706 // here merely indicates successfully starting the thread and does not 707 // imply successful termination/execution. 708 return OK; 709 710 // Exiting scope of mLock is a memory barrier and allows new thread to run 711}
【推荐】编程新体验,更懂你的AI,立即体验豆包MarsCode编程助手
【推荐】凌霞软件回馈社区,博客园 & 1Panel & Halo 联合会员上线
【推荐】抖音旗下AI助手豆包,你的智能百科全书,全免费不限次数
【推荐】博客园社区专享云产品让利特惠,阿里云新客6.5折上折
【推荐】轻量又高性能的 SSH 工具 IShell:AI 加持,快人一步
· 浏览器原生「磁吸」效果!Anchor Positioning 锚点定位神器解析
· 没有源码,如何修改代码逻辑?
· 一个奇形怪状的面试题:Bean中的CHM要不要加volatile?
· [.NET]调用本地 Deepseek 模型
· 一个费力不讨好的项目,让我损失了近一半的绩效!
· 在鹅厂做java开发是什么体验
· 百万级群聊的设计实践
· WPF到Web的无缝过渡:英雄联盟客户端的OpenSilver迁移实战
· 永远不要相信用户的输入:从 SQL 注入攻防看输入验证的重要性
· 浏览器原生「磁吸」效果!Anchor Positioning 锚点定位神器解析