|
From: Xavier de G. <xd...@gm...> - 2015-02-18 17:02:03
|
Pyclewn 2.0, a Vim front-end to the gdb and pdb debuggers, has been released at http://pyclewn.sourceforge.net/ New features ^^^^^^^^^^^^ * Three clewn buffers are updated by gdb, they list the breakpoints, the backtrace and the threads. One can jump with the <CR> key or the mouse to the corresponding source code line from the ``(clewn)_breakpoints`` window or switch to the corresponding frame from the ``(clewn)_backtrace`` window, or switch to the correponding thread with the ``(clewn)_threads`` window. The ``Ccwindow`` command has been removed. * All the Vim functions defined by pyclewn that split windows can be overriden. * A compound watched variable in ``(clewn)_variables`` can be expanded and collapsed with the <CR> key or the mouse. * The new ``Cballooneval`` command switches on/off the Vim balloon without interfering with the pyclewn key mappings that rely on the Vim 'ballooneval' option to be functional. * The first optional argument of the ``:Pyclewn`` Vim command selects the debugger and the following arguments are passed to the debugger. For example, to debug ``foobar args`` with gdb, run the Vim commmand ``:Pyclewn gdb --args foobar args``. * The new ``g:pyclewn_terminal`` Vim global variable allows the pyclewn program started with ``:Pyclewn`` to run in a terminal instead of as a daemon, and helps trouble shooting startup problems. Changes ^^^^^^^ * Windows support has been removed. Pyclewn runs now on Python 2.7 or Python 3.2 or newer and the same source code is used for all those Python versions. Pyclewn uses now asyncio (or trollius on Python versions that do not support asyncio, i.e. version 2.7 or older than 3.4) instead of the deprecated asyncore Python module. * The preferred method to install pyclewn is ``pip``. The Vim run time files are installed with a vimball. Local installation is done using the Python user scheme instead of the home scheme. pdb-clone is installed separately from PyPI. * The pyclewn program is now started with the command ``python -m clewn`` followed by the options and an optional argument that selects which debugger to run. * The ``(clewn)_console`` window is only created at the first ``C`` command. * Pointers are not dereferenced anymore in the Vim balloon and the ``nodereference`` keyword of the ``--gdb`` option is now ignored. As a result, gdb Python-based pretty-printers output is displayed in the balloon. * ``CTRL-E`` is a standard Vim command, it is replaced with ``CTRL-K`` in pyclewn key mappings for clearing breakpoints. The ``(clewn)_console`` is not any more popped up after hitting a pyclewn mapped key. * The watched variables clewn buffer is now named ``(clewn)_variables`` and the installed Vim syntax file has been renamed from ``dbgvar.vim`` to ``clewn_variables.vim``. Bug fixes ^^^^^^^^^ * When pyclewn is started from a terminal, the controlling terminal of the gdb inferior process is now correctly set to the terminal from where pyclewn has been started. * The terminal spawned by the ``inferiortty`` command is now automatically closed at the end of each debugging session. * Fix a gdb version parsing error on the non-conformant Cygwin versions of gdb. See the bug report at http://cygwin.com/ml/cygwin/2014-06/msg00211.html. * Fix the problem that changes made to the plugin global variables after the first invocation of ``:Pyclewn`` are ignored. * Pyclewn listens on '127.0.0.1' and each debugger type uses now a different netbeans port number. * Pyclewn prevents now the spawning of a terminal by ``Cinferiortty`` also when the inferior is stopped in a shared library. * Fix the problem that when the first command is ``Cbreak``, the breakpoint is not highlighted. Xavier |