已关闭
[Bug]: Crash During AttachCurrentThread Caused by Incorrect Stack Base Offset in ThreadGetStackInfo #11165
dingbihan创建于 4月29日关闭于 6月3日
4月29日 添加了label：bug
openharmony_ci
4月29日 评论：
4月29日 评论：
感谢提交Issue！关于Issue的交互操作，请访问OpenHarmony社区支持命令清单。如果有问题，请联系 [@weng-changcheng](https://gitcode.com/weng-changcheng) [@godmiaozi](https://gitcode.com/godmiaozi) [@liyiming13](https://gitcode.com/liyiming13) [@lijin1039](https://gitcode.com/lijin1039) [@Prof](https://gitcode.com/Prof) [@dingding5](https://gitcode.com/dingding5) [@vpukhov](https://gitcode.com/vpukhov) [@v-cherkashin](https://gitcode.com/v-cherkashin) 。如果需要调整订阅PR、Issue的变更状态，请访问链接。
Thanks for submitting the issue. For more commands, please visit OpenHarmony Command List. If you have any questions, please refer to committer gitcode for help. If you need to change the subscription of a Pull Request or Issue, please visit the link.
4月29日 添加了label：waiting_for_assign
dingbihan4月29日 关联了pull request：Crash During AttachCurrentThread Caused by Incorrect Stack Base Offset in ThreadGetStackInfo
4月29日 关联了pull request：Crash During AttachCurrentThread Caused by Incorrect Stack Base Offset in ThreadGetStackInfo
6月3日 关闭了 issue
6月3日 issue状态由 待办的 改变为 已完成
感谢对OpenHarmony社区的支持与关注，欢迎反馈缺陷。
发生了什么问题？
The process crashed during AttachCurrentThread() on an FFRT worker thread while initializing stack overflow protection for a newly attached Ark coroutine.
期望行为是什么？
AttachCurrentThread() should complete successfully, and stack boundaries should be initialized consistently without causing duplicate stack offset or crash.
如何复现该缺陷
Run the RemoteCommunicationKitHttpCacheTest001 test case in the current test application and trigger the RCP/ANI path on an OS_FFRT_* worker thread.
其他补充信息
版本或分支信息
[x] master
[ ] Release 6.1
[ ] Release 6.0
[ ] Release 5.1.0
[ ] Release 5.0.3
[ ] Release 4.1
[ ] Other