llvm-project.git/lldb/scripts/verify_api.py, branch users/nico/python-1 Unnamed repository; edit this file 'description' to name the repository. [lldb] Format Python files in scripts and utils (#66053) 2023-09-14T07:54:02+00:00 David Spickett david.spickett@linaro.org 2023-09-14T07:54:02+00:00 602e47c5f9fd2e14c7bfb6111e6558fa0d27c87f Using: black --exclude "third_party/" ./lldb/ 
Using:
black --exclude "third_party/" ./lldb/
 [lldb] NFC: Fix trivial typo in comments, documents, and messages 2020-04-06T16:06:16+00:00 Kazuaki Ishizaki ishizaki@jp.ibm.com 2020-04-06T16:06:02+00:00 e9264b746b81a63323d884ea07b2ebfbb660d004 Differential Revision: https://reviews.llvm.org/D77460 
Differential Revision: https://reviews.llvm.org/D77460
python 2/3 compat: commands vs subprocess 2019-03-26T14:46:15+00:00 Serge Guelton sguelton@redhat.com 2019-03-26T14:46:15+00:00 1a12dd70c00a44e34384b1904d18d309ae3c3ac6 Differential Revision: https://reviews.llvm.org/D59584 llvm-svn: 356995 
Differential Revision: https://reviews.llvm.org/D59584

llvm-svn: 356995
Python 2/3 compatibility: from __future__ import print_function 2019-03-21T18:27:40+00:00 Serge Guelton sguelton@redhat.com 2019-03-21T18:27:40+00:00 525cd59f5a12254e80d5f20bf2d9713728a114d4 Differential Revision: https://reviews.llvm.org/D59580 llvm-svn: 356695 
Differential Revision: https://reviews.llvm.org/D59580

llvm-svn: 356695
*** This commit represents a complete reformatting of the LLDB source code 2016-09-06T20:57:50+00:00 Kate Stone katherine.stone@apple.com 2016-09-06T20:57:50+00:00 b9c1b51e45b845debb76d8658edabca70ca56079 *** to conform to clang-format’s LLVM style. This kind of mass change has *** two obvious implications: Firstly, merging this particular commit into a downstream fork may be a huge effort. Alternatively, it may be worth merging all changes up to this commit, performing the same reformatting operation locally, and then discarding the merge for this particular commit. The commands used to accomplish this reformatting were as follows (with current working directory as the root of the repository): find . \( -iname "*.c" -or -iname "*.cpp" -or -iname "*.h" -or -iname "*.mm" \) -exec clang-format -i {} + find . -iname "*.py" -exec autopep8 --in-place --aggressive --aggressive {} + ; The version of clang-format used was 3.9.0, and autopep8 was 1.2.4. Secondly, “blame” style tools will generally point to this commit instead of a meaningful prior commit. There are alternatives available that will attempt to look through this change and find the appropriate prior commit. YMMV. llvm-svn: 280751 
*** to conform to clang-format’s LLVM style.  This kind of mass change has
*** two obvious implications:

Firstly, merging this particular commit into a downstream fork may be a huge
effort.  Alternatively, it may be worth merging all changes up to this commit,
performing the same reformatting operation locally, and then discarding the
merge for this particular commit.  The commands used to accomplish this
reformatting were as follows (with current working directory as the root of
the repository):

    find . \( -iname "*.c" -or -iname "*.cpp" -or -iname "*.h" -or -iname "*.mm" \) -exec clang-format -i {} +
    find . -iname "*.py" -exec autopep8 --in-place --aggressive --aggressive {} + ;

The version of clang-format used was 3.9.0, and autopep8 was 1.2.4.

Secondly, “blame” style tools will generally point to this commit instead of
a meaningful prior commit.  There are alternatives available that will attempt
to look through this change and find the appropriate prior commit.  YMMV.

llvm-svn: 280751
Added the ability to verify the LLDB API on MacOSX using a script. Usage is: 2012-08-30T21:21:24+00:00 Greg Clayton gclayton@apple.com 2012-08-30T21:21:24+00:00 0274766be5914317cb4947fa169dbe55ff4aec6b ./verify_api.py --library ./LLDB.framework/LLDB --api-regex lldb --arch x86_64 /Applications/Xcode.app/Contents/PlugIns/DebuggerLLDB.ideplugin/Contents/MacOS/DebuggerLLDB So you specify a library with the "--library" option, then you specify an API regular expression that you want to match the executables against with "--api-regex <regex>", here we specify "lldb" to catch all undefined external API functions from the binary we want to test, then we specify the architectures to check with "--arch <arch>" (this can be specified more than once), and you give one or more executables. llvm-svn: 162941 
./verify_api.py --library ./LLDB.framework/LLDB --api-regex lldb --arch x86_64 /Applications/Xcode.app/Contents/PlugIns/DebuggerLLDB.ideplugin/Contents/MacOS/DebuggerLLDB

So you specify a library with the "--library" option, then you specify an API regular expression that you want to match the executables against with "--api-regex <regex>", here we specify "lldb" to catch all undefined external API functions from the binary we want to test, then we specify the architectures to check with "--arch <arch>" (this can be specified more than once), and you give one or more executables.

llvm-svn: 162941