| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[lldb] Remove a few unused .exports files They used to be referenced from the .xcodeproj files, but those are long gone. No behavior change. Differential Revision: https://reviews.llvm.org/D107444 | 4 年前 | |
Don't re-define constants that are now in compact_unwind_encoding.h. | 4 年前 | |
[lldb][NFC] Use C++ versions of the deprecated C standard library headers The C headers are deprecated so as requested in D102845, this is replacing them all with their (not deprecated) C++ equivalent. Reviewed By: shafik Differential Revision: https://reviews.llvm.org/D103084 | 5 年前 | |
the thread id is easier to read in base16. llvm-svn: 326849 | 8 年前 | |
[lldb][NFC] Add maybe_unused to err used in asserts (#98055) | 2 年前 | |
[feature] add clang-tidy hook to pre-commit config Co-authored-by: wiyr0<wangyixian3@huawei.com> # message auto-generated for no-merge-commit merge: !163 merge feature/add-clang-tidy-hook into master [feature] add clang-tidy hook to pre-commit config Created-by: wiyr0 Commit-by: wiyr0 Merged-by: ascend-robot Description: ### 1. 修改描述 - **修改原因:** https://gitcode.com/Ascend/msot/issues/54 - **修改方案:** 新增 clang-tidy hook,使用 lldb/.clang-tidy 作为配置(通过 InheritParentConfig 继承根配置并禁用 readability-identifier-naming) - **修改内容:**  - [ ] **涉及代码双合**(贴上另一个PR链接): ---- ### 2. 功能验证 - [x] **功能自验截图**(请确保不体现个人信息) - [x] **冒烟是否通过**  ---- ### 3. 代码检视 - **要求:** - 合入功能代码大于 200 行,需要sig会议申报代码检视议题,并在PR中标注会议。 - committer评估是否需要在sig会议进行代码检视。 - 参与检视的committer人员名单与检视时间。 - 大于 1000 行代码原则上不允许合入,需进行备案。 - [x] **是否经过代码检视** - [ ] **是否具备UT测试用例看护** - [ ] **是否需要在sig会议中进行代码检视** - **检视committer人员名单与检视时间:** ---- ### 4. 资料修改自检 - **资料修改:** ---- See merge request: Ascend/msdebug!163 | 11 天前 | |
[lldb] Format more Python files with black (#65979) By running this from lldb/ $ black --exclude "third_party/|scripts/|utils/" ./ | 2 年前 | |
Add lldb version into initialize response lldb-dap (#98703) Frequently, while troubleshooting user's debugging issues in VScode, we would like to know lldb version so that we can confirm if certain patch/feature is in or not. This PR adds version string into initialize response so that telemetry can track it. --------- Co-authored-by: jeffreytan81 <jeffreytan@fb.com> | 2 年前 | |
[lldb] Revise IDE folder structure (#89748) Update the folder titles for targets in the monorepository that have not seen taken care of for some time. These are the folders that targets are organized in Visual Studio and XCode ( set_property(TARGET <target> PROPERTY FOLDER "<title>")) when using the respective CMake's IDE generator. * Ensure that every target is in a folder * Use a folder hierarchy with each LLVM subproject as a top-level folder * Use consistent folder names between subprojects * When using target-creating functions from AddLLVM.cmake, automatically deduce the folder. This reduces the number of set_property/set_target_property, but are still necessary when add_custom_target, add_executable, add_library, etc. are used. A LLVM_SUBPROJECT_TITLE definition is used for that in each subproject's root CMakeLists.txt. | 2 年前 | |
Revert "Remove the LINK_COMPONENTS entry from lldb-instr CMakery" This reverts commit e12a950d90f88aeddaa97d6e7c8fd0bfedc42f73. D142241 broke -sBUILD_SHARED_LIBS=ON build. After investigations in https://github.com/llvm/llvm-project/issues/60314, the issue that prompted D142441 now seems gone. Fixes https://github.com/llvm/llvm-project/issues/60314. Reviewed By: JDevlieghere Differential Revision: https://reviews.llvm.org/D145181 | 3 年前 | |
added all modifications made for msdebug | 7 个月前 | |
[lldb][test] Fix lldb-test compile error https://github.com/llvm/llvm-project/pull/82819 made the lookup here ambiguous. | 2 年前 | |
[bugfix] halMemAdvise劫持及内存属性管理优化 Co-authored-by: wiyr0<wangyixian3@huawei.com> # message auto-generated for no-merge-commit merge: !219 merge feature/hal-mem-advise-hijack into master [bugfix] halMemAdvise劫持及内存属性管理优化 Created-by: wiyr0 Commit-by: wiyr0 Merged-by: ascend-robot Description: ### 1. 修改描述 - **修改原因:** 1. halMemAdvise接口缺少劫持,无法追踪和缓存内存属性设置,导致每次设置断点时重复调用halMemAdvise,且kernel执行后未恢复原始内存属性。 2. 由于原因1,且halMemAdvise的接口不能重复设置相同的属性,会有日志报错。这样一个kernel.o多次不同的kernel launch,会导致第二次kernel launch的时候,由于.o的内存属性已经被设置过了,获取start_pc的接口里也会调用halMemAdvise接口,这样就会报错。影响断点设置,**更严重会影响算子运行不成功甚至掉卡** - **修改方案:** 1. 劫持halMemAdvise, 拿到内存的属性信息 2. 每次做内存可读写设置前,先保存内存原有属性,在kernel运行结束后,再还原内存属性,这里就直接用thread local 结构体在Launch前保存原有的内存属性信息 3. halMemAdvise本身位于驱动接口,这里就做了一些公共函数的提取 - **修改内容:** 1. 新增extern "C" halMemAdvise劫持函数,成功时将(ptr,device)->advise记录到全局map;acl.h声明,version.map导出符号 2. 新增MemAdviseRestoreInfo结构体(runtime_stub.h)及GetMemAdviseRestoreInfo()(static thread_local),LaunchKernelPre/SetMemoryWritable中保存原始属性,LaunchKernelPost中通过RestoreMemAdvise恢复 3. 提取halMemAdviseOrigin、SetMemAdviseIfNecessary、RestoreMemAdvise共享函数供两文件复用;GetPcStartAddr拆分为GetRawPcStartAddr/FixPcStartAddr/EnableMemReadWrite - [ ] **涉及代码双合**(贴上另一个PR链接): ---- ### 2. 功能验证 - [x] **功能自验截图**(请确保不体现个人信息) main_scalar:   add_simt:  add_simd:  simt_rma_ub2gm: 不设置断点:  设置断点:   - [x] **冒烟是否通过**  ---- ### 3. 代码检视 - **要求:** - 合入功能代码大于 200 行,需要sig会议申报代码检视议题,并在PR中标注会议。 - committer评估是否需要在sig会议进行代码检视。 - 参与检视的committer人员名单与检视时间。 - 大于 1000 行代码原则上不允许合入,需进行备案。 - [x] **是否经过代码检视** - [ ] **是否具备UT测试用例看护** - [ ] **是否需要在sig会议中进行代码检视** - **检视committer人员名单与检视时间:** ---- ### 4. 资料修改自检 - **资料修改:** 不涉及 ---- See merge request: Ascend/msdebug!219 | 8 天前 | |
[fixbug] 多线程下调试器错停于内部断点&构建问题 Co-authored-by: wangyixian<wangyixian3@huawei.com> # message auto-generated for no-merge-commit merge: !45 merge fix_bug into master [fixbug] 多线程下调试器错停于内部断点&构建问题 Created-by: wiyr0 Commit-by: wangyixian Merged-by: ascend-robot Description: ### 1. 修改描述 - **修改原因:** 1. 多线程的场景里,内部断点触发时,出现了某个线程也是sigtrap的中断,此时client端会认为多个线程出现sigtrap中断,需要stop。 2. 算子多卡场景里,若劫持函数是多线程被调用下,发送kernel信息的劫持函数,易出现覆盖现象,导致该发送kernel的卡没发送kernel信息 3. 某些构建环境下,构建出来的liblldb.so一来libform.so - **修改方案:** 1. 强行修改非主线程的中断信号 2. 加锁 3. 增加libform.so.5的交付件 - **修改内容:** 1. 当前为内部断点事件时,强行修改非主线程的中断信号为0号 2. 给sentBinaries map加个局部静态锁。 3. 参考libpanel.so的加法,增加libform.so.5的交付件 4. 删除不再使用到的函数 - [ ] **涉及代码双合**(贴上另一个PR链接):NA ---- ### 2. 功能验证 - [x] **功能自验截图**(请确保不体现个人信息)   - [x] **冒烟是否通过** ---- ### 3. 代码检视 - **要求:** - 合入功能代码大于 200 行,需要sig会议申报代码检视议题,并在PR中标注会议。 - committer评估是否需要在sig会议进行代码检视。 - 参与检视的committer人员名单与检视时间。 - 大于 1000 行代码原则上不允许合入,需进行备案。 - [x] **是否经过代码检视** - [ ] **是否具备UT测试用例看护** NA - [ ] **是否需要在sig会议中进行代码检视** NA - **检视committer人员名单与检视时间:** ---- ### 4. 资料修改自检 - **资料修改:** NA ---- See merge request: Ascend/msdebug!45 | 4 个月前 | |
[lldb] Rename lldb-vscode to lldb-dap (#69264) Rename lldb-vscode to lldb-dap. This change is largely mechanical. The following substitutions cover the majority of the changes in this commit: s/VSCODE/DAP/ s/VSCode/DAP/ s/vscode/dap/ s/g_vsc/g_dap/ Discourse RFC: https://discourse.llvm.org/t/rfc-rename-lldb-vscode-to-lldb-dap/74075/ | 2 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 4 年前 | ||
| 4 年前 | ||
| 5 年前 | ||
| 8 年前 | ||
| 2 年前 | ||
| 11 天前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 3 年前 | ||
| 7 个月前 | ||
| 2 年前 | ||
| 8 天前 | ||
| 4 个月前 | ||
| 2 年前 |