👋 您好,欢迎向 MindStudio-Debugger 提交 Issue!
我们已收到您的反馈,感谢你对开源社区的支持。🎉
📅 处理时效 维护团队将在工作日 24 小时内查看并回复您的问题。
🔍 自助排查(推荐优先查看) 在等待回复期间,您可以先查阅以下资源,多数问题可快速解决:
- MindStudio-Debugger 官方文档
- 历史 Issue 中相似问题的解决方案
💡 **为了更快定位问题,请您确保 Issue 包含:
- 清晰的问题描述
- 可复现的操作步骤
- 相关日志、截图或环境信息
我们会尽快跟进,感谢您的理解与配合!


udma_demo以及cann-samples仓中2_Performance/moe_init_routing_story打不住断点 :udma_demo目前环境问题没跑起来,根据提供的截图分析,断点位置在host侧代码,且断点位置算子并不会运行到;moe_init_rounting_story算子因为环境驱动太老,跑卡死了


simt_rma_ub2gm算子,工具拉起算子工程报错 是工具问题,在修复


0729已合入


验证通过:
(py_311) [root@localhost simt_rma_ub2gm]# msdebug -- bash run.sh
>>>>> MindStudio <<<<<
THE END-TO-END TOOLCHAIN TO UNLEASH HUAWEI ASCEND COMPUTE
=================================================================
msdebug 26.0.0
(msdebug) target create "bash"
Current executable set to '/usr/bin/bash' (aarch64).
(msdebug) settings set -- target.run-args "run.sh"
Cannot read termcap database;
using dumb terminal settings.
(msdebug) b main.cpp:44
Breakpoint 1: no locations (pending on future shared library load).
WARNING: Unable to resolve breakpoint to any actual locations.
(msdebug) r
Process 3306961 launched: '/usr/bin/bash' (aarch64)
Process 3306961 stopped and restarted: thread 1 received signal: SIGCHLD
Process 3306961 stopped and restarted: thread 1 received signal: SIGCHLD
Process 3306961 stopped and restarted: thread 1 received signal: SIGCHLD
3307133 background process recorded
3307134 background process recorded
[Launch of Kernel _Z24barrier_on_stream_kernelim on Device 0]
[Launch of Kernel _Z24barrier_on_stream_kernelim on Device 1]
[Launch of Kernel Z9demo_callPiS_S on Device 0]
[Launch of Kernel Z9demo_callPiS_S on Device 1]
[Launch of Kernel _Z24barrier_on_stream_kernelim on Device 0]
1 location added to breakpoint 1
Process 3306961 stopped
[Switching to focus on Kernel Z9demo_callPiS_S, CoreId 0, Type aiv]
- thread #1, name = 'bash', stop reason = breakpoint 1.1
frame #0: 0x0000120040811d40 device_debugdata_1`demo_call(origin=, res_prev= , res_next= ) at main.cpp:44:5
41 int32_t prev_pe = (mype - 1 + npes) % npes;
42 int32_t next_pe = (mype + 1) % npes;
43
-> 44 asc_vf_call<transfer_data>(dim3(32), origin, res_prev, res_next, COPY_SIZE, prev_pe, next_pe, mype);
45 }
46
47 void run_demo_mem(void* stream, int32_t* origin, int32_t* res_prev, int32_t* res_next)
(msdebug) s
Process 3306961 stopped
[Switching to focus on Kernel Z9demo_callPiS_S, CoreId 0, Type aiv] - thread #1, name = 'bash', stop reason = step in
frame #0: 0x00001200408110c8 device_debugdata_1`void asc_vf_call<&transfer_data(int AS1*, int AS1*, int AS1*, unsigned int, int, int, int), int AS1*&, int AS1*&, int AS1*&, int const&, int&, int&, int&>(args=0x0000000000197e98, args=0x0000000000197e90, args=0x0000000000197e88, args=0x0000120040811e98, args=0x0000000000197e80, args=0x0000000000197e7c, args=0x0000000000197e84) (.vector) at common_functions.h:40:32
37 aicore inline void asc_vf_call(dim3 threadNums, Args &&...args)
38 {
39 #if defined(SPLIT_CORE_VEC) || defined(ASCENDC_CPU_DEBUG)
-> 40 cce::async_invoke(threadNums, args...);
41 #endif
42 }
43 #endif


在提交新问题之前,请确保您已经在社区中搜索过相关问题,并使用了社区中提供的资源/工具后,仍未找到满意的解决方式。
⚠️ 安全信息提醒:请仔细检查提供的文本内容,确保其不包含敏感数据信息,包括但不限于:
在分享配置信息或代码示例时,请将敏感信息脱敏处理,或使用
<TOKEN>等占位符替代原有内容。环境信息
🐛 问题描述
【问题描述】
shmem算子,simt_rma_ub2gm算子,工具拉起算子工程报错,单独运行算子正常;udma_demo打不住断点
【环境信息】
ubuntu
【重现步骤】
1、1、git clone https://gitcode.com/cann/shmem.git
2、vi shmem/CMakeLists.txt添加编译选项并同时注释Werror和-DL2_CACHE_HINT
add_compile_options(
-D_FORTIFY_SOURCE=2
-O0 -g -std=c++17
#-Werror
avoid ascendc interference
#-DL2_CACHE_HINT
-DTILING_KEY_VAR
-fstack-protector-strong
3、编译算子
source /home/dds/B111/Ascend/ascend-toolkit/set_env.sh
bash scripts/build.sh -examples -soc_type Ascend950
cd /home/dds/shmem/examples/simt_rma_ub2gm
bash run.sh
msdebug --bash run.sh
cd /home/dds/shmem/examples/udma_demo
msdebug -- bash run.sh 1
b udma_demo_kernel.cpp:50
r
【预期结果】
能成功打住断点
【实际结果】
simt_rma_ub2gm算子,工具拉起算子工程报错,单独运行算子正常;udma_demo打不住断点
欢迎加入社区,感谢您对社区的贡献 🎉!