/openbsd-src/gnu/llvm/lldb/docs/resources/ |
H A D | caveats.rst | 9 Python subtitle 12 LLDB has a powerful scripting interface which is accessible through Python. 13 Python is available either from within LLDB through a (interactive) script 14 interpreter, or as a Python module which you can import from the Python 17 To make this possible, LLDB links against the Python shared library. Linking 18 against Python comes with some constraints to be aware of. 20 1. It is not possible to build and link LLDB against a Python 3 library and 21 use it from Python 2 and vice versa. 24 Python and use it through an interpreter coming from another distribution. 25 For example, on macOS, if you build and link against Python from [all …]
|
/openbsd-src/usr.sbin/unbound/ |
H A D | acx_python.m4 | 3 # Allow the use of a (user set) custom python version 5 AC_ARG_VAR([PYTHON_VERSION],[The installed Python 7 will be appended to the Python interpreter 10 AC_PATH_PROG([PYTHON],[python[$PYTHON_VERSION]]) 11 if test -z "$PYTHON"; then 12 AC_MSG_ERROR([Cannot find 'python$PYTHON_VERSION' in your system path. You can use the environment variable 'PYTHON_VERSION=version_number' for an explicit version.]) 17 PYTHON_VERSION=`$PYTHON -c "import sys; \ 34 # on Debian 10, for python 2.7 and 3.7. So, we check the version, 49 AC_MSG_CHECKING([for the $m Python modul [all...] |
/openbsd-src/gnu/llvm/lldb/bindings/python/ |
H A D | CMakeLists.txt | 12 -python 17 ${CMAKE_CURRENT_SOURCE_DIR}/python.swig 19 COMMENT "Building LLDB Python wrapper") 28 OUTPUT ${LLVM_RUNTIME_OUTPUT_INTDIR}/lldb-python 30 COMMAND ${CMAKE_COMMAND} -E copy lldb-python ${LLVM_RUNTIME_OUTPUT_INTDIR}/lldb-python 33 add_custom_target(lldb-python-wrapper ALL DEPENDS 34 ${LLVM_RUNTIME_OUTPUT_INTDIR}/lldb-python 45 "${LLDB_SOURCE_DIR}/bindings/python/createPythonInit.py" 56 # Add a Post-Build Event to copy over Python files and create the symlink to 57 # liblldb.so for the Python API(hardlink on Windows). [all …]
|
H A D | python.swig | 11 "The lldb module contains the public APIs for Python binding. 40 a way that is incompatible with our usage of the python module as __init__.py 52 # Relative import should work if we are being loaded by Python. 55 // These versions will not generate working python modules, so error out early. 116 %include "python-typemaps.swig" 121 #include "../source/Plugins/ScriptInterpreter/Python/PythonDataObjects.h" 122 #include "../source/Plugins/ScriptInterpreter/Python/SWIGPythonBridge.h" 123 #include "../bindings/python/python-swigsafecast.swig" 125 using namespace lldb_private::python; 130 %include "python-extensions.swig" [all …]
|
H A D | get-python-config.py | 18 parser = argparse.ArgumentParser(description="extract cmake variables from python") 23 # to where lldb's python libraries will be installed. 26 # PYTHON'S prefix to where python libraries are supposed to be 29 # The result is if LLDB and python are give the same prefix, then 30 # lldb's python lib will be put in the correct place for python to find it. 39 print('lib/python%d.%d/site-packages' % sys.version_info[:2])
|
/openbsd-src/gnu/llvm/llvm/utils/lit/tests/Inputs/shtest-not/ |
H A D | not-calls-external.txt | 7 # RUN: not %{python} fail.py 8 # RUN: not not %{python} pass.py 9 # RUN: not not not %{python} fail.py 10 # RUN: not not not not %{python} pass.py 15 # RUN: not not --crash %{python} pass.py 16 # RUN: not not --crash %{python} fail.py 17 # RUN: not not --crash not %{python} pass.py 18 # RUN: not not --crash not %{python} fail.py 26 # RUN: env not %{python} fail.py | FileCheck -check-prefixes=FOO-NO,BAR-NO %s 27 # RUN: not env %{python} fail.py | FileCheck -check-prefixes=FOO-NO,BAR-NO %s [all …]
|
/openbsd-src/usr.bin/file/magdir/ |
H A D | python | 1 # $OpenBSD: python,v 1.2 2008/05/08 01:40:57 chl Exp $ 4 # python: file(1) magic for python 8 0 string """ a python script text executable 9 # MAGIC as specified in Python/import.c (1.5 to 2.3.0a) 11 0 belong 0x994e0d0a python 1.5/1.6 byte-compiled 12 0 belong 0x87c60d0a python 2.0 byte-compiled 13 0 belong 0x2aeb0d0a python 2.1 byte-compiled 14 0 belong 0x2ded0d0a python 2.2 byte-compiled 15 0 belong 0x3bf20d0a python 2.3 byte-compiled 16 0 belong 0x6df20d0a python 2.4 byte-compiled [all …]
|
/openbsd-src/regress/sys/netinet6/rip6cksum/ |
H A D | Makefile | 5 # scapy powerful interactive packet manipulation in python 16 PYTHON = python3 -u ${.CURDIR}/ macro 34 ${PYTHON}sendrecv.py -r 8 -s 32 40 ${PYTHON}sendrecv.py -i -r 32 -s 32 46 ${PYTHON}sendrecv.py -r 8 -s 32 52 ${PYTHON}sendrecv.py -c 0 -r 8 -s 32 58 ${PYTHON}sendrecv.py -i -r 0 -s 0 64 ${PYTHON}sendrecv.py -i -r 1 -s 1 70 ${PYTHON}sendrecv.py -c 0 -s 2 76 ${PYTHON}sendrec [all...] |
/openbsd-src/gnu/llvm/lldb/packages/Python/lldbsuite/test/ |
H A D | README-TestSuite | 2 to the Python test suite under the current 'test' directory. 26 turn inherits from Python's unittest.TestCase. The concrete subclass can 31 start with the letters test. For more details about the Python's unittest 32 framework, go to http://docs.python.org/library/unittest.html. 44 Most of them predate the introduction of the python test suite and contain 49 part of the Python-based test suite to test lldb functionality. 52 C/C++/ObjC source files; they were created to house the Python test case which 66 directory or via supplying a Python dictionary to the build method in your 67 Python test script. An example of the latter can be found in 96 Many new features were added to unittest in Python 2.7, including test [all …]
|
H A D | lldb_pylint_helper.py | 11 Provides helper support for adding lldb test paths to the python path. 30 """Adds lldb test-related paths to the python path. 35 child test_runner/lib directory will be added to the python 41 to reliably lint lldb python test scripts (including the test 46 … import sys; sys.path.append(os.path.expanduser("~/path/to/lldb/packages/Python/lldbsuite/test"));… 52 pylint will use the python files in whichever tree it is run from. 64 python directories to your path. 72 and this will properly lint that file, using the lldb-specific python 79 looking for the lldb test infrastructure python library paths. 101 on the lldb python module path. [all …]
|
/openbsd-src/regress/sys/net/pf_opts/ |
H A D | Makefile | 24 # scapy powerful interactive packet manipulation in python 115 # Create python include file containing the addresses. 158 PYTHON = python3 -u ./ macro 160 PYTHON = env PYTHONPATH=${.OBJDIR} python3 -u ${.CURDIR}/ macro 207 ${SUDO} /sbin/route -T ${N1} exec ${PYTHON}icmp.py N1 208 ${SUDO} /sbin/route -T ${N2} exec ${PYTHON}icmp.py N2 212 ${SUDO} /sbin/route -T ${N1} exec ${PYTHON}icmp6.py N1 213 ${SUDO} /sbin/route -T ${N2} exec ${PYTHON}icmp6.py N2 229 ${SUDO} /sbin/route -T ${N1} exec ${PYTHON}icmp6_hop.py N1 230 ${SUDO} /sbin/route -T ${N2} exec ${PYTHON}icmp6_hop.py N2 [all …]
|
/openbsd-src/gnu/llvm/lldb/docs/use/ |
H A D | python.rst | 1 Python Scripting 5 ways -- a Unix Python session can initiate/run a debug session 6 non-interactively using LLDB; and within the LLDB debugger tool, Python 11 Python scripting to find a bug in a program that searches for text in a 56 impractical. Therefore we will write a Python script to search the tree 62 Python would look like, with line numbers added for easy reference in 97 Before we can call any Python function on any of our program's 98 variables, we need to get the variable into a form that Python can 101 binary search tree, put into a Python variable. The second parameter is 106 The most interesting parameter is the first one, the Python variable [all …]
|
H A D | python-reference.rst | 1 Python Reference 4 The entire LLDB API is available as Python functions through a script bridging 5 interface. This means the LLDB API's can be used directly from python either 6 interactively or to build python apps that provide debugger features. 8 Additionally, Python can be used as a programmatic interface within the lldb 19 The LLDB API is contained in a python module named lldb. A useful resource when 20 writing Python extensions is the lldb Python classes reference guide. 31 lldb - The lldb module contains the public APIs for Python binding. 34 … /System/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/Python/lldb/__init__.py 57 Or you can get help using any python object, here we use the lldb.process [all …]
|
/openbsd-src/gnu/llvm/llvm/utils/valgrind/ |
H A D | i386-pc-linux-gnu.supp | 9 # Python false positives according to 10 # http://svn.python.org/projects/python/trunk/Misc/README.valgrind 15 obj:/usr/bin/python* 21 obj:/usr/bin/python* 27 obj:/usr/bin/python* 37 We don't care if python leaks 40 obj:/usr/bin/python*
|
H A D | x86_64-pc-linux-gnu.supp | 8 # Python false positives according to 9 # http://svn.python.org/projects/python/trunk/Misc/README.valgrind 14 obj:/usr/bin/python* 20 obj:/usr/bin/python* 26 obj:/usr/bin/python* 56 We don't care if python leaks 59 obj:/usr/bin/python*
|
/openbsd-src/gnu/llvm/lldb/source/Plugins/ScriptInterpreter/Python/ |
H A D | ScriptedPythonInterface.cpp | 15 // LLDB Python header must be included first 16 #include "lldb-python.h" 33 python::PythonObject &p, Status &error) { in ExtractValueFromPythonObject() 34 python::PythonList result_list(python::PyRefType::Borrowed, p.get()); in ExtractValueFromPythonObject() 41 StructuredData::DictionarySP>(python::PythonObject &p, Status &error) { in ExtractValueFromPythonObject() 42 python::PythonDictionary result_dict(python::PyRefType::Borrowed, p.get()); in ExtractValueFromPythonObject() 48 python::PythonObject &p, Status &error) { in ExtractValueFromPythonObject() 61 python::PythonObject &p, Status &error) { in ExtractValueFromPythonObject() 77 std::optional<MemoryRegionInfo>>(python::PythonObject &p, Status &error) { in ExtractValueFromPythonObject()
|
H A D | SWIGPythonBridge.h | 19 // LLDB Python header must be included first 20 #include "lldb-python.h" 22 #include "Plugins/ScriptInterpreter/Python/PythonDataObjects.h" 36 namespace python { 40 python::PythonObject ToSWIGHelper(void *obj, swig_type_info *info); 84 python::ScopedPythonObject<lldb::SBCommandReturnObject> 86 python::ScopedPythonObject<lldb::SBEvent> ToSWIGWrapper(Event *event); 88 } // namespace python 99 python::PythonObject LLDBSwigPythonCreateScriptedObject( 126 python::PythonObject [all …]
|
H A D | ScriptedPythonInterface.h | 37 T ExtractValueFromPythonObject(python::PythonObject &p, Status &error) { in ExtractValueFromPythonObject() 43 using namespace python; in Dispatch() local 51 return ErrorWithMessage<T>(caller_signature, "Python object ill-formed", in Dispatch() 62 "Python implementor not allocated.", error); in Dispatch() 81 "Python method could not be called.", error); in Dispatch() 90 // Now that we called the python method with the transformed arguments, in Dispatch() 116 python::PythonObject Transform(Status arg) { in Transform() 117 return python::ToSWIGWrapper(arg); in Transform() 127 void ReverseTransform(T &original_arg, python::PythonObject transformed_arg, in ReverseTransform() 178 fmt += python::PythonFormat<T>::format; in FormatArgs() [all …]
|
H A D | lldb-python.h | 1 //===-- lldb-python.h -------------------------------------------*- C++ -*-===// 21 // Python.h needs to be included before any system headers in order to avoid 28 // need to ensure this doesn't happen. At the same time, Python.h will also try 35 // may be different from the value that Python defines it to be which results 36 // in a warning. Undefine _POSIX_C_SOURCE before including Python.h The same 42 // Include locale before Python so _PY_PORT_CTYPE_UTF8_ISSUE doesn't cause 48 // Include python for non windows machines 49 #include <Python.h>
|
H A D | ScriptInterpreterPythonImpl.h | 16 #include "lldb-python.h" 386 python::PythonModule &GetMainModule(); 388 python::PythonDictionary &GetSessionDictionary(); 390 python::PythonDictionary &GetSysModuleDictionary(); 398 python::PythonObject &save_file, const char *mode); 400 python::PythonObject m_saved_stdin; 401 python::PythonObject m_saved_stdout; 402 python::PythonObject m_saved_stderr; 403 python::PythonModule m_main_module; 404 python::PythonDictionary m_session_dict; [all …]
|
/openbsd-src/gnu/llvm/lldb/scripts/ |
H A D | install_custom_python.py | 1 """ Copies the build output of a custom python interpreter to a directory 2 structure that mirrors that of an official Python distribution. 8 Python distribution installed on their system. Occasionally 9 a user may want to build their own version of Python, and on 13 official Python distribution, thus allowing PYTHONHOME to be 66 # includes the Python executables, python27(_d).dll, and relevant PDB 68 print('Copying Python executables...') 77 'python', 'pythonw'], [ 82 print('Copying Python include directory') 85 # Copy Lib folder (builtin Python modules) [all …]
|
/openbsd-src/gnu/llvm/lldb/cmake/modules/ |
H A D | FindPythonAndSwig.cmake | 5 # Find the python interpreter and libraries as a whole. 8 # Use PYTHON_HOME as a hint to find Python 3. 13 # The install name for the Python 3 framework in Xcode is relative to 21 # The check below shouldn't match Homebrew's Python framework as it is 22 # called Python.framework instead of Python3.framework. 43 message(STATUS "SWIG 3 or later is required for Python support in LLDB but could not be found") 51 # able to detect whether Python was built with assertions, and only Windows 52 # has the requirement that Debug LLDB must use Debug Python.
|
/openbsd-src/share/man/man5/ |
H A D | python-module.5 | 1 .\" $OpenBSD: python-module.5,v 1.15 2025/01/17 08:52:01 sthen Exp $ 28 .Dt PYTHON-MODULE 5 31 .Nm python-module 32 .Nd lang/python port module 35 .Li MODULES=lang/python 40 By default, the module builds ports using Python 3. 41 For legacy ports using Python 2, 97 Most modern Python software can be packaged using a PEP 517 build 127 Python 2 and some older Python [all...] |
/openbsd-src/gnu/llvm/clang/bindings/python/tests/ |
H A D | CMakeLists.txt | 1 # Test target to run Python test suite from main build. 5 add_custom_target(check-clang-python 14 set_target_properties(check-clang-python PROPERTIES FOLDER "Clang tests") 37 # The Python FFI interface is broken on AIX: https://bugs.python.org/issue38628. 44 # SystemZ has broken Python/FFI interface: 52 LLVM_ALL_ADDITIONAL_TEST_TARGETS check-clang-python)
|
/openbsd-src/gnu/llvm/llvm/docs/ |
H A D | GettingStartedVS.rst | 57 If you would like to run the LLVM tests you will need `Python 58 <http://www.python.org/>`_. Version 3.6 and newer are known to work. You can 59 install Python with Visual Studio 2019, from the Microsoft store or from 60 the `Python web site <http://www.python.org/>`_. We recommend the latter since it 70 These instruction were tested with Visual Studio 2019 and Python 3.9.6: 77 4. Download and install the latest `Python 3 release <http://www.python.org/>`_. 79 and **Add Python to the PATH**. This will allow installing psutil for all 80 users for the regression tests and make Python available from the command 85 7. Complete the Python installation. 217 c:\llvm> python ..\build\Release\bin\llvm-lit.py llvm\test [all …]
|