| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[lldb][docs] Resolve the remaining sphinx formatter warnings in the SB API docs With this patch there should no longer be any warnings when generating the SB API sphinx docs. | 5 年前 | |
[lldb][docs] Cleanup the Python doc strings for SB API classes The first line of the doc string ends up on the SB API class summary at the root page of the Python API web page of LLDB. Currently many of the descriptions are missing or are several lines which makes the table really hard to read. This just adds the missing docstrings where possible and fixes the formatting where necessary. | 5 年前 | |
[lldb] Clarify docstring for SBBlock::IsInlined, NFC Previously, there was a little ambiguity about whether IsInlined should return true for an inlined lexical block, since technically the lexical block would not represent an inlined function (it'd just be contained within one). Edit suggested by Jim Ingham. | 5 年前 | |
[lldb] Use internal_dict name over dict in python examples Follow up to https://reviews.llvm.org/rG483ec136da7193de781a5284f1c37929cc27c05c | 5 年前 | |
[lldb] Use internal_dict name over dict in python examples Follow up to https://reviews.llvm.org/rG483ec136da7193de781a5284f1c37929cc27c05c | 5 年前 | |
[lldb][docs] Translate ASCII art to restructured text formatting This translates most of the old ASCII art in our documentation to the equivalent in restructured text (which the new version of the LLDB docs is using). | 5 年前 | |
[lldb][docs] Resolve the remaining sphinx formatter warnings in the SB API docs With this patch there should no longer be any warnings when generating the SB API sphinx docs. | 5 年前 | |
feat: add cjthread API Signed-off-by: yuanchao <yuanchao55@h-partners.com> | 1 个月前 | |
[lldb/API] Add a way to check if the CommandInterpreter is interactive This patch adds the ability for the user to check if the command interpreter's IOHandler is interactive. Differential Revision: https://reviews.llvm.org/D119499 Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com> | 4 年前 | |
[lldb/API] Add CommandInterpreter::{Get,Set}PrintErrors to SBAPI (NFC) This patch exposes the getter and setter methods for the command interpreter print_errors run option. rdar://74816984 Differential Revision: https://reviews.llvm.org/D98001 Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com> | 5 年前 | |
[lldb][docs] Translate ASCII art to restructured text formatting This translates most of the old ASCII art in our documentation to the equivalent in restructured text (which the new version of the LLDB docs is using). | 5 年前 | |
[lldb][docs] Cleanup the Python doc strings for SB API classes The first line of the doc string ends up on the SB API class summary at the root page of the Python API web page of LLDB. Currently many of the descriptions are missing or are several lines which makes the table really hard to read. This just adds the missing docstrings where possible and fixes the formatting where necessary. | 5 年前 | |
[lldb/API] Turn SBCompileUnit::GetIndexForLineEntry into FindLineEntryIndex (NFC) This patch renames the SBCompileUnit::GetIndexForLineEntry api to be an overload of SBCompileUnit::FindLineEntryIndex Differential Revision: https://reviews.llvm.org/D125594 Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com> | 4 年前 | |
[lldb/API] Add SetDataWithOwnership method to SBData This patch introduces a new method to SBData: SetDataWithOwnership. Instead of referencing the pointer to the data, this method copies the data buffer into lldb's heap memory. This can prevent having the underlying DataExtractor object point to freed/garbage-collected memory. Differential Revision: https://reviews.llvm.org/D115652 Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com> | 4 年前 | |
Add LoadTraceFromFile to SBDebugger and SBTrace Add trace load functionality to SBDebugger via the LoadTraceFromFile method. Update intelpt test case class to have testTraceLoad method so we can take advantage of the testApiAndSB decorator to test both the CLI and SB without duplicating code. Differential Revision: https://reviews.llvm.org/D128107 | 3 年前 | |
[lldb/Bindings] Move bindings into their own subdirectory All the code required to generate the language bindings for Python and Lua lives under scripts, even though the majority of this code aren't scripts at all, and surrounded by scripts that are totally unrelated. I've reorganized these files and moved everything related to the language bindings into a new top-level directory named bindings. This makes the corresponding files self contained and much more discoverable. Differential revision: https://reviews.llvm.org/D72437 | 6 年前 | |
[lldb][docs] Translate ASCII art to restructured text formatting This translates most of the old ASCII art in our documentation to the equivalent in restructured text (which the new version of the LLDB docs is using). | 5 年前 | |
[lldb][docs] Translate ASCII art to restructured text formatting This translates most of the old ASCII art in our documentation to the equivalent in restructured text (which the new version of the LLDB docs is using). | 5 年前 | |
[lldb][docs] Translate ASCII art to restructured text formatting This translates most of the old ASCII art in our documentation to the equivalent in restructured text (which the new version of the LLDB docs is using). | 5 年前 | |
[lldb][docs] Cleanup the Python doc strings for SB API classes The first line of the doc string ends up on the SB API class summary at the root page of the Python API web page of LLDB. Currently many of the descriptions are missing or are several lines which makes the table really hard to read. This just adds the missing docstrings where possible and fixes the formatting where necessary. | 5 年前 | |
[lldb] NFC: Fix trivial typo in comments, documents, and messages Differential Revision: https://reviews.llvm.org/D77460 | 6 年前 | |
[lldb][docs] Use inline literals for code/paths instead of rendering it with the default role Right now we're using the 'content' role as default which will just render these things as cursive (which isn't really useful for code examples). It also prevents us from assigning a more useful default role in the future. | 5 年前 | |
[lldb][docs] Translate ASCII art to restructured text formatting This translates most of the old ASCII art in our documentation to the equivalent in restructured text (which the new version of the LLDB docs is using). | 5 年前 | |
[lldb][docs] Cleanup the Python doc strings for SB API classes The first line of the doc string ends up on the SB API class summary at the root page of the Python API web page of LLDB. Currently many of the descriptions are missing or are several lines which makes the table really hard to read. This just adds the missing docstrings where possible and fixes the formatting where necessary. | 5 年前 | |
[lldb][docs] Use inline literals for code/paths instead of rendering it with the default role Right now we're using the 'content' role as default which will just render these things as cursive (which isn't really useful for code examples). It also prevents us from assigning a more useful default role in the future. | 5 年前 | |
[lldb][docs] Translate ASCII art to restructured text formatting This translates most of the old ASCII art in our documentation to the equivalent in restructured text (which the new version of the LLDB docs is using). | 5 年前 | |
[lldb][docs] Cleanup the Python doc strings for SB API classes The first line of the doc string ends up on the SB API class summary at the root page of the Python API web page of LLDB. Currently many of the descriptions are missing or are several lines which makes the table really hard to read. This just adds the missing docstrings where possible and fixes the formatting where necessary. | 5 年前 | |
[lldb][docs] Cleanup the Python doc strings for SB API classes The first line of the doc string ends up on the SB API class summary at the root page of the Python API web page of LLDB. Currently many of the descriptions are missing or are several lines which makes the table really hard to read. This just adds the missing docstrings where possible and fixes the formatting where necessary. | 5 年前 | |
[lldb][docs] Translate ASCII art to restructured text formatting This translates most of the old ASCII art in our documentation to the equivalent in restructured text (which the new version of the LLDB docs is using). | 5 年前 | |
[lldb][docs] Add a doc page for enums and constants Enums and constants are currently missing in the new LLDB Python API docs. In theory we could just let them be autogenerated like the SB API classes, but sadly the generated documentation suffers from a bunch of problems. Most of these problems come from the way SWIG is representing enums, which is done by translating every single enum case into its own constant. This has a bunch of nasty effects: * Because SWIG throws away the enum types, we can't actually reference the enum type itself in the API. Also because automodapi is impossible to script, this can't be fixed in post (at least without running like sed over the output files). * The lack of enum types also causes that every enum *case* has its own full doc page. Having a full doc page that just shows a single enum case is pointless and it really slows down sphinx. * There is no SWIG code for the enums, so there is also no place to write documentation strings for them. Also there is no support for copying the doxygen strings (which would be in the wrong format, but better than nothing) for enums (let alone our defines), so we can't really document all this code. * Because the enum cases are just forwards to the native lldb module (which we mock), automodapi actually takes the Mock docstrings and adds it to every single enum case. I don't see any way to solve this via automodapi or SWIG. The most reasonable way to solve this is IMHO to write a simple Clang tool that just parses our enum/constant headers and emits an *.rst file that we check in. This way we can do all the LLDB-specific enum case and constant grouping that we need to make a readable documentation page. As we're without any real documentation until I get around to write that tool, I wrote a doc page for the enums/constants as a stop gap measure. Most of this is done by just grepping our enum header and then manually cleaning up all the artifacts and copying the few doc strings we have. Reviewed By: JDevlieghere Differential Revision: https://reviews.llvm.org/D94959 | 5 年前 | |
[lldb/Commands] Add command options for ScriptedProcess to ProcessLaunch This patch adds a new command options to the CommandObjectProcessLaunch for scripted processes. Among the options, the user need to specify the class name managing the scripted process. The user can also use a key-value dictionary holding arbitrary data that will be passed to the managing class. This patch also adds getters and setters to SBLaunchInfo for the class name managing the scripted process and the dictionary. rdar://65508855 Differential Review: https://reviews.llvm.org/D95710 Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com> | 5 年前 | |
[lldb][docs] Cleanup the Python doc strings for SB API classes The first line of the doc string ends up on the SB API class summary at the root page of the Python API web page of LLDB. Currently many of the descriptions are missing or are several lines which makes the table really hard to read. This just adds the missing docstrings where possible and fixes the formatting where necessary. | 5 年前 | |
[lldb] Fix two documentation typos | 5 年前 | |
[lldb/Plugins] Add memory region support in ScriptedProcess This patch adds support for memory regions in Scripted Processes. This is necessary to read the stack memory region in order to reconstruct each stackframe of the program. In order to do so, this patch makes some changes to the SBAPI, namely: - Add a new constructor for SBMemoryRegionInfo that takes arguments such as the memory region name, address range, permissions ... This is used when reading memory at some address to compute the offset in the binary blob provided by the user. - Add a GetMemoryRegionContainingAddress method to SBMemoryRegionInfoList to simplify the access to a specific memory region. With these changes, lldb is now able to unwind the stack and reconstruct each frame. On top of that, reloading the target module at offset 0 allows lldb to symbolicate the ScriptedProcess using debug info, similarly to an ordinary Process. To test this, I wrote a simple program with multiple function calls, ran it in lldb, stopped at a leaf function and read the registers values and copied the stack memory into a binary file. These are then used in the python script. Differential Revision: https://reviews.llvm.org/D108953 Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com> | 4 年前 | |
[lldb/Plugins] Add memory region support in ScriptedProcess This patch adds support for memory regions in Scripted Processes. This is necessary to read the stack memory region in order to reconstruct each stackframe of the program. In order to do so, this patch makes some changes to the SBAPI, namely: - Add a new constructor for SBMemoryRegionInfo that takes arguments such as the memory region name, address range, permissions ... This is used when reading memory at some address to compute the offset in the binary blob provided by the user. - Add a GetMemoryRegionContainingAddress method to SBMemoryRegionInfoList to simplify the access to a specific memory region. With these changes, lldb is now able to unwind the stack and reconstruct each frame. On top of that, reloading the target module at offset 0 allows lldb to symbolicate the ScriptedProcess using debug info, similarly to an ordinary Process. To test this, I wrote a simple program with multiple function calls, ran it in lldb, stopped at a leaf function and read the registers values and copied the stack memory into a binary file. These are then used in the python script. Differential Revision: https://reviews.llvm.org/D108953 Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com> | 4 年前 | |
[LLVM] update cangjie llvm +feature_macos_expr +bugfix_cjdb_update_ios +bugfix_cjdb_expr_multi_modules +bugfix_cjdb_expr_mutil_modules +feature-black-hole +feature_dev_compiler_cross +feature_cjdb_main2dev +windows-native-build +bugfix_llvm_bugfix_to_main_0801 +bugfix_cjdb_nested_generic_func | 9 个月前 | |
[lldb/API] Add ability to check if module is backed by a file on disk This patch introduces a new SBAPI method: SBModule::IsFileBacked As the name suggests, it tells the user if the module's object file is on disk or in memory. rdar://68538278 Differential Revision: https://reviews.llvm.org/D118261 Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com> | 4 年前 | |
[lldb][docs] Cleanup the Python doc strings for SB API classes The first line of the doc string ends up on the SB API class summary at the root page of the Python API web page of LLDB. Currently many of the descriptions are missing or are several lines which makes the table really hard to read. This just adds the missing docstrings where possible and fixes the formatting where necessary. | 5 年前 | |
[lldb] Introduce SBPlatform::SetSDKRoot It complements the existing SBDebugger::SetCurrentPlatformSDKRoot and allows one to set the sysroot of a platform without making it current. Differential Revision: https://reviews.llvm.org/D117550 | 4 年前 | |
feat: add cjthread api Signed-off-by: yuanchao <yuanchao55@h-partners.com> | 1 个月前 | |
Revert "[LLDB/API] Expose args and env from SBProcessInfo." This reverts commit 8d33437d030af27fff21dd3fd0e66893b0148217. This broke one of the buildbots. | 4 年前 | |
[lldb][docs] Cleanup the Python doc strings for SB API classes The first line of the doc string ends up on the SB API class summary at the root page of the Python API web page of LLDB. Currently many of the descriptions are missing or are several lines which makes the table really hard to read. This just adds the missing docstrings where possible and fixes the formatting where necessary. | 5 年前 | |
[lldb][docs] Cleanup the Python doc strings for SB API classes The first line of the doc string ends up on the SB API class summary at the root page of the Python API web page of LLDB. Currently many of the descriptions are missing or are several lines which makes the table really hard to read. This just adds the missing docstrings where possible and fixes the formatting where necessary. | 5 年前 | |
[lldb][docs] Cleanup the Python doc strings for SB API classes The first line of the doc string ends up on the SB API class summary at the root page of the Python API web page of LLDB. Currently many of the descriptions are missing or are several lines which makes the table really hard to read. This just adds the missing docstrings where possible and fixes the formatting where necessary. | 5 年前 | |
[lldb] add SBSection.alignment to python bindings This commit adds SBSection.GetAlignment(), and SBSection.alignment as a python property to lldb. Reviewed By: clayborg, JDevlieghere, labath Differential Revision: https://reviews.llvm.org/D128069 | 3 年前 | |
[lldb][docs] Translate ASCII art to restructured text formatting This translates most of the old ASCII art in our documentation to the equivalent in restructured text (which the new version of the LLDB docs is using). | 5 年前 | |
[lldb][docs] Translate ASCII art to restructured text formatting This translates most of the old ASCII art in our documentation to the equivalent in restructured text (which the new version of the LLDB docs is using). | 5 年前 | |
[lldb][docs] Cleanup the Python doc strings for SB API classes The first line of the doc string ends up on the SB API class summary at the root page of the Python API web page of LLDB. Currently many of the descriptions are missing or are several lines which makes the table really hard to read. This just adds the missing docstrings where possible and fixes the formatting where necessary. | 5 年前 | |
[trace][intel-pt] Create basic SB API This adds a basic SB API for creating and stopping traces. Note: This doesn't add any APIs for inspecting individual instructions. That'd be a more complicated change and it might be better to enhande the dump functionality to output the data in binary format. I'll leave that for a later diff. This also enhances the existing tests so that they test the same flow using both the command interface and the SB API. I also did some cleanup of legacy code. Differential Revision: https://reviews.llvm.org/D103500 | 4 年前 | |
[lldb][docs] Translate ASCII art to restructured text formatting This translates most of the old ASCII art in our documentation to the equivalent in restructured text (which the new version of the LLDB docs is using). | 5 年前 | |
[lldb][docs] Translate ASCII art to restructured text formatting This translates most of the old ASCII art in our documentation to the equivalent in restructured text (which the new version of the LLDB docs is using). | 5 年前 | |
[NFC] fix a typo | 4 年前 | |
Don't report memory return values on MacOS_arm64 of SysV_arm64 ABI's. They don't require that the memory return address be restored prior to function exit, so there's no guarantee the value is correct. It's better to return nothing that something that's not accurate. Differential Revision: https://reviews.llvm.org/D121348 | 4 年前 | |
[lldb] [gdb-remote] Support getting siginfo via API Add Thread::GetSiginfo() and SBThread::GetSiginfo() methods to retrieve the siginfo value from server. Differential Revision: https://reviews.llvm.org/D118055 | 4 年前 | |
[lldb/Bindings] Move bindings into their own subdirectory All the code required to generate the language bindings for Python and Lua lives under scripts, even though the majority of this code aren't scripts at all, and surrounded by scripts that are totally unrelated. I've reorganized these files and moved everything related to the language bindings into a new top-level directory named bindings. This makes the corresponding files self contained and much more discoverable. Differential revision: https://reviews.llvm.org/D72437 | 6 年前 | |
[lldb] [gdb-remote server] Introduce new stop reasons for fork and vfork Introduce three new stop reasons for fork, vfork and vforkdone events. This includes server support for serializing fork/vfork events into gdb-remote protocol. The stop infos for the two base events take a pair of PID and TID for the newly forked process. Differential Revision: https://reviews.llvm.org/D100196 | 5 年前 | |
[trace] Add an option to save a compact trace bundle A trace bundle contains many trace files, and, in the case of intel pt, the largest files are often the context switch traces because they are not compressed by default. As a way to improve this, I'm adding a --compact option to the trace save command that filters out unwanted processes from the context switch traces. Eventually we can do the same for intel pt traces as well. Differential Revision: https://reviews.llvm.org/D129239 | 3 年前 | |
[lldb] Add SBType::IsAggregateType Add IsAggregateType to the SB API. I'd like to use this from tests, and there are numerous other Is<X>Type predicates on SBType. Differential Revision: https://reviews.llvm.org/D121252 | 4 年前 | |
[lldb/Bindings] Move bindings into their own subdirectory All the code required to generate the language bindings for Python and Lua lives under scripts, even though the majority of this code aren't scripts at all, and surrounded by scripts that are totally unrelated. I've reorganized these files and moved everything related to the language bindings into a new top-level directory named bindings. This makes the corresponding files self contained and much more discoverable. Differential revision: https://reviews.llvm.org/D72437 | 6 年前 | |
[lldb][docs] Cleanup the Python doc strings for SB API classes The first line of the doc string ends up on the SB API class summary at the root page of the Python API web page of LLDB. Currently many of the descriptions are missing or are several lines which makes the table really hard to read. This just adds the missing docstrings where possible and fixes the formatting where necessary. | 5 年前 | |
[lldb/Bindings] Move bindings into their own subdirectory All the code required to generate the language bindings for Python and Lua lives under scripts, even though the majority of this code aren't scripts at all, and surrounded by scripts that are totally unrelated. I've reorganized these files and moved everything related to the language bindings into a new top-level directory named bindings. This makes the corresponding files self contained and much more discoverable. Differential revision: https://reviews.llvm.org/D72437 | 6 年前 | |
[lldb/Bindings] Move bindings into their own subdirectory All the code required to generate the language bindings for Python and Lua lives under scripts, even though the majority of this code aren't scripts at all, and surrounded by scripts that are totally unrelated. I've reorganized these files and moved everything related to the language bindings into a new top-level directory named bindings. This makes the corresponding files self contained and much more discoverable. Differential revision: https://reviews.llvm.org/D72437 | 6 年前 | |
[lldb/Bindings] Move bindings into their own subdirectory All the code required to generate the language bindings for Python and Lua lives under scripts, even though the majority of this code aren't scripts at all, and surrounded by scripts that are totally unrelated. I've reorganized these files and moved everything related to the language bindings into a new top-level directory named bindings. This makes the corresponding files self contained and much more discoverable. Differential revision: https://reviews.llvm.org/D72437 | 6 年前 | |
[lldb/Bindings] Move bindings into their own subdirectory All the code required to generate the language bindings for Python and Lua lives under scripts, even though the majority of this code aren't scripts at all, and surrounded by scripts that are totally unrelated. I've reorganized these files and moved everything related to the language bindings into a new top-level directory named bindings. This makes the corresponding files self contained and much more discoverable. Differential revision: https://reviews.llvm.org/D72437 | 6 年前 | |
[lldb/Bindings] Move bindings into their own subdirectory All the code required to generate the language bindings for Python and Lua lives under scripts, even though the majority of this code aren't scripts at all, and surrounded by scripts that are totally unrelated. I've reorganized these files and moved everything related to the language bindings into a new top-level directory named bindings. This makes the corresponding files self contained and much more discoverable. Differential revision: https://reviews.llvm.org/D72437 | 6 年前 | |
[lldb/Bindings] Move bindings into their own subdirectory All the code required to generate the language bindings for Python and Lua lives under scripts, even though the majority of this code aren't scripts at all, and surrounded by scripts that are totally unrelated. I've reorganized these files and moved everything related to the language bindings into a new top-level directory named bindings. This makes the corresponding files self contained and much more discoverable. Differential revision: https://reviews.llvm.org/D72437 | 6 年前 | |
[formatters] Add a formatter for libstdc++ optional Besides adding the formatter and the summary, this makes the libcxx tests also work for this case. This is the polished version of https://reviews.llvm.org/D114266, authored by Danil Stefaniuc. Differential Revision: https://reviews.llvm.org/D114403 | 4 年前 | |
[lldb][docs] Translate ASCII art to restructured text formatting This translates most of the old ASCII art in our documentation to the equivalent in restructured text (which the new version of the LLDB docs is using). | 5 年前 | |
[lldb][docs] Cleanup the Python doc strings for SB API classes The first line of the doc string ends up on the SB API class summary at the root page of the Python API web page of LLDB. Currently many of the descriptions are missing or are several lines which makes the table really hard to read. This just adds the missing docstrings where possible and fixes the formatting where necessary. | 5 年前 | |
[lldb][docs] Translate ASCII art to restructured text formatting This translates most of the old ASCII art in our documentation to the equivalent in restructured text (which the new version of the LLDB docs is using). | 5 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 1 个月前 | ||
| 4 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 3 年前 | ||
| 6 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 6 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 9 个月前 | ||
| 4 年前 | ||
| 5 年前 | ||
| 4 年前 | ||
| 1 个月前 | ||
| 4 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 3 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 4 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 6 年前 | ||
| 5 年前 | ||
| 3 年前 | ||
| 4 年前 | ||
| 6 年前 | ||
| 5 年前 | ||
| 6 年前 | ||
| 6 年前 | ||
| 6 年前 | ||
| 6 年前 | ||
| 6 年前 | ||
| 6 年前 | ||
| 4 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 |