pyclewn-general — User discussion for pyclewn.

[pyclewn] Newbie question about the (clewn)_console

[Abhishek K. <abh...@gm...>]

Hi,
I am using vim(7.4 with netbeans) via tmux after sshing into the
development server that is not running X. I am evaluating if pyclewn would
meet my python debugging needs through vim. My question is does the vim
buffer (identified by (clewn)_console is readonly by design for PDB or I
have got something horribly wrong with my setup?

Coming from ConqueGDB (another vim plugin for similar task), I was
expecting that I can change the buffer to edit (insert mode) and then fire
away commands on the (pdb) prompt. However when I press 'i' for insert
mode, the message flashes "Netbean does not allow to change read only
files".

I searched archives and found just on similar question for gdb which went
unanswered. Google is not helping as well. So either something incredibly
rare (or stupid) has happened with my setup.

Please indicate or set the expectation right as I need to be up and running
very fast on this,

Thanks for your help.

Cheers!


  <http://www.heartfulness.org/>
Experience Heartfulness <http://www.heartfulness.org/>

Re: [pyclewn] Vim Crashing With SEGV When Calling Cfile

[jsn <jsn...@gm...>]

> On 21-Jul-2016, at 05:36, Xavier de Gaye <xd...@gm...> wrote:
> 
> On 07/21/2016 07:39 AM, jsn wrote:
> > I am trying to run pyclewn to debug my C++ program on Linux.  When I run the Cfile command in gvim, gvim crashes, and it says:
> >
> > /dev/pts/25 pseudo terminal created.
> > Vim: Caught deadly signal SEGV
> > Vim: Finished.
> >
> 
> Hi John,
> 
> IMHO the obvious step would have been to report the problem to the Vim
> developers since it is a Vim crash.


You're right.  Sorry.

Re: [pyclewn] Vim Crashing With SEGV When Calling Cfile

[Xavier de G. <xd...@gm...>]

On 07/21/2016 11:36 AM, Xavier de Gaye wrote:
 > On 07/21/2016 07:39 AM, jsn wrote:
 >> I am trying to run pyclewn to debug my C++ program on Linux.  When I run the Cfile command in gvim, gvim crashes, and it says:
 >>
 >> /dev/pts/25 pseudo terminal created.
 >> Vim: Caught deadly signal SEGV
 >> Vim: Finished.
 >>
 >> Here is the command I use on the bash command-line to start pyclewn:
 >>
 >> python3 -m clewn -e gvim -c main.cpp -l debug -f pyclewn.log
 >>
 >> And gvim starts fine, showing 4 or 5 spit windows (I assume they are coming up correctly).  Then I enter the Cfile command (:Cfile ~/path/to/my/exe), and it crashes immediately.
 >> I have attached the log file to this message (I'm not sure if attachments work on this list).
 >>
 >> Here is some system info:
 >> Ubuntu Linux 16.04
 >> Python 3.5.2
 >> Pyclewn: 2.3
 >> vim: 7.4 patches 1-1907 (GTK2-GNOME GUI; including +netbeans_intg +python3/dyn +python/dyn)
 >
 >
 > Hi John,
 >
 > IMHO the obvious step would have been to report the problem to the Vim
 > developers since it is a Vim crash.
 >
 > Maybe the problem is related to
 > http://thread.gmane.org/gmane.editors.vim.devel/60263
 > The corresponding patch has been committed at
 > http://thread.gmane.org/gmane.editors.vim.devel/60269
 >


I must add that it is really sad that the Vim developers do extensive
changes to the netbeans interface without ever running any test.

-- 
Xavier

Les Chemins de Lokoti: http://lokoti.alwaysdata.net

Re: [pyclewn] Vim Crashing With SEGV When Calling Cfile

[Xavier de G. <xd...@gm...>]

On 07/21/2016 07:39 AM, jsn wrote:
 > I am trying to run pyclewn to debug my C++ program on Linux.  When I run the Cfile command in gvim, gvim crashes, and it says:
 >
 > /dev/pts/25 pseudo terminal created.
 > Vim: Caught deadly signal SEGV
 > Vim: Finished.
 >
 > Here is the command I use on the bash command-line to start pyclewn:
 >
 > python3 -m clewn -e gvim -c main.cpp -l debug -f pyclewn.log
 >
 > And gvim starts fine, showing 4 or 5 spit windows (I assume they are coming up correctly).  Then I enter the Cfile command (:Cfile ~/path/to/my/exe), and it crashes immediately.
 > I have attached the log file to this message (I'm not sure if attachments work on this list).
 >
 > Here is some system info:
 > Ubuntu Linux 16.04
 > Python 3.5.2
 > Pyclewn: 2.3
 > vim: 7.4 patches 1-1907 (GTK2-GNOME GUI; including +netbeans_intg +python3/dyn +python/dyn)


Hi John,

IMHO the obvious step would have been to report the problem to the Vim
developers since it is a Vim crash.

Maybe the problem is related to
http://thread.gmane.org/gmane.editors.vim.devel/60263
The corresponding patch has been committed at
http://thread.gmane.org/gmane.editors.vim.devel/60269

-- 
Xavier

Les Chemins de Lokoti: http://lokoti.alwaysdata.net

[pyclewn] Vim Crashing With SEGV When Calling Cfile

[jsn <jsn...@gm...>]

I am trying to run pyclewn to debug my C++ program on Linux.  When I run
the Cfile command in gvim, gvim crashes, and it says:

/dev/pts/25 pseudo terminal created.
Vim: Caught deadly signal SEGV
Vim: Finished.

Here is the command I use on the bash command-line to start pyclewn:

python3 -m clewn -e gvim -c main.cpp -l debug -f pyclewn.log

And gvim starts fine, showing 4 or 5 spit windows (I assume they are coming
up correctly).  Then I enter the Cfile command (:Cfile ~/path/to/my/exe),
and it crashes immediately.
I have attached the log file to this message (I'm not sure if attachments
work on this list).

Here is some system info:
Ubuntu Linux 16.04
Python 3.5.2
Pyclewn: 2.3
vim: 7.4 patches 1-1907 (GTK2-GNOME GUI; including +netbeans_intg
+python3/dyn +python/dyn)

I would really apprecite it, if someone can let me know what steps I can
take to debug this problem.
Thank you.

--
John

[pyclewn] Noob . Please help me test Pyclewn

[Adam Z. <zed...@gm...>]

Hello , so I have read about Pyclewn and it sounds amazing. I am currently
in the process of testing it. However I am not sure what I might be doing
wrong . Here is what i have in my current dir that i would like to test it
on

custom.h
custom.cpp
main.cpp
out

The out file is the output of the main.cpp. Now i would like to test it
with Pyclewn. Here is what I did
in my terminal I did the following:

Step :1 launch macvim through terminal
>mvim
launches macvim

Step: 2 run pyclewn from mvim
:Pyclewn

Pyclewn starts up and then my screen looks like this


​
Now I would like to set a breakpoint in my first statement so I do this
:Cmapkeys

as a result i get the response
Error: netbeans is not connected

Why am i getting that ? I would like to set a breakpoint and run it. Am i
doing something wrong ? any suggestions would be appreciated

[pyclewn] Noob : mac-Vim pyclewn fails to start

[Rajesh K. <raj...@gm...>]

I am getting an error when I attempt to start pyclewn in macvim
any suggestions. Following is what i tried in vim.

:Pyclewn
Starting pyclewn.
Running nbstart, <C-C> to interrupt.
...................
The 'Pyclewn' command has been aborted.
Error: pyclewn failed to start.
To get the cause of the problem set the global variable 'pyclewn_terminal'
to:
:let g:pyclewn_terminal = "xterm, -e"
Press the <Enter> key to continue.

Re: [pyclewn] Debugging curses application remote terminal

[Xavier de G. <xd...@gm...>]

Hi Joey

Two ways to debug a curses application:
1. attach to the running curses application whose pid is PROCESS-ID:
     :Pyclewn
     :Cfile app
     :Cattach PROCESS-ID

2. start the curses application from pyclewn, and run the application in a new terminal, note that Cinferiortty must be run before the application is started:
     :Pyclewn
     :Cfile app
     :Cinferiortty
     :Cstart

-- 
Xavier

Les Chemins de Lokoti: http://lokoti.alwaysdata.net

[pyclewn] Debugging curses application remote terminal

[Joey E. <jce...@gm...>]

I'm trying to debug an application that requires i/o.  It can never connect
to the terminal. I've tried a bunch of different things. Is there a
tutorial for this?

I would like to:

1- run vim
2- run Pyclewn
3- Cfile app
4- Crun

I'm using tmux.  Is there a way to have it create a new window?

-Joey

[pyclewn] [ANN] pyclewn release 2.3

[Xavier de G. <xd...@gm...>]

Pyclewn 2.3 has been released at http://pyclewn.sourceforge.net/

Pyclewn is a Python program that allows the use of Vim as a front end to the
GNU debugger gdb and the Python debugger pdb.

New features
^^^^^^^^^^^^

* A dynamic watch variable, for example an STL container, is now displayed
   using the enabled gdb pretty printers.

* Support `gdb background execution`.

Changes
^^^^^^^

* Line numbers are included in the backtrace window, except at the top level
   frame (to avoid screen blinks when stepping). Breakpoint conditions are
   listed in the breakpoint window.

Bug fixes
^^^^^^^^^

* Issue #41: Fix the 'define', 'commands' and 'document' gdb commands
   (regression).

* Issue #42: The 'python' gdb command can also be used now as a multi-line
   command.

* Issue #43: The 'shell' gdb command is an illegal command as already stated
   in the documentation.

* Fix the following exception upon starting with python3.6:
   ``in create_server: sock.bind(sa): TypeError: an integer is required (got
   type str)``.

* Issue #46: Fix an exception caused by the incorrect parsing of the output of
   the ``-thread-info`` gdb/mi command.

* Issue #47: Loading the list of source file names may be very slow for large
   libraries with debugging symbols. Only load the list of source file names
   upon running a ``file``-like gdb command or when a library is being loaded.
   Previously, this list was instead loaded on ``file``-like and ``break``-like
   gdb commands.

* Issue #48: Fix a vim keymap error when the command prefix has been set to
   another value that the default ``C``.

* Issue #49: The line marker is not missing now after a gdb background
   ``continue&`` command.

* Issue #50: The breakpoint and backtrace windows always print now the source
   file basename followed by the absolute pathname in angle brackets.

-- 
Xavier

Les Chemins de Lokoti: http://lokoti.alwaysdata.net

Re: [pyclewn] Pyclewn- how to get pretty printers on watch variables list for STL containers?

[Xavier de G. <xd...@gm...>]

The watch variables use pretty printers now when enabled, to display STL containers. This has been fixed at issue #40 by changeset 35d9e13b7bcf.

To use this feature without waiting for the next release, you can build Pyclewn from the BitBucket repository as described at http://pyclewn.sourceforge.net/install.html in the section named 
"Installing from the development version at BitBucket".  Note that you will be building 2.3 and not 2.2, so you need to s/2.2/2.3/ in the description.  Note that you will also have to use the 
--ignore-installed option of pip when upgrading later to the latest release, as pip will not upgrade when the installed version is the same as the target version.

There are some limitations that are listed in the documentation as follows:

                                                     *pyclewn-dynamic-variable*
A dynamic watched variable is displayed using a gdb pretty printer.  When the
variable is a container (for example an STL container), the display uses round
brackets instead of square brackets around the expansion marker "+" or "-".
There are currently some limitations with using dynamic watched variables:

     * Gdb does not update the elements of a nested container when the
       container is dynamic, so it is not very useful to expand a nested
       container.
     * It is not possible to delete an element of a dynamic container,
       one can only delete the whole container (gdb issue 19321).
     * It is not possible to collapse a dynamic container (gdb issue 19321).

--
Xavier

Les Chemins de Lokoti: http://lokoti.alwaysdata.net

Re: [pyclewn] Pyclewn- how to get pretty printers on watch variables list for STL containers?

[Xavier de G. <xd...@gm...>]

Currently it is not possible to enable pretty printers in (clewn)_variables.

There is an '-enable-pretty-printing' command in gdb/mi Variable Objects that does the job. When this command is run, variable objects are pretty printable and become 'dynamic', which means that the 
logic used to browse them is different (children are dynamically learned by the gdb front end with a 'has_more' flag).

I will implement this shortly.

Xavier

[pyclewn] Pyclewn- how to get pretty printers on watch variables list for STL containers?

[ricky s. <luc...@gm...>]

I have python pretty printers enabled on my system. Print and display work
fine but

the watch variable list gives the raw container output.Is there a way to
enable pretty printers in (clewn)_variables list?This is what the output
looks like on the (clewn)_variables buffer.

[-] var1: (std::vector<int, std::allocator<int> >) v ={=} {...}

  [+] var1.std::_Vector_base<int, std::allocator<int> >: ()
std::_Vector_base<int, std::allocator<int> > ={=}

[-] var2: (std::__cxx11::string                  ) s ={=} {...}

  [-] var2.public : () public  ={=}

     *  var2.public.npos: (const std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >::size_type) npos ={=}
18446744073709551615

  [-] var2.private: () private ={=}

    [+] var2.private._M_dataplus     : (
                                                       ) _M_dataplus
={*}

     *  var2.private._M_string_length: (std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >::size_type) _M_string_length
 ={*} 11

    [+] var2.private.2_anonymous     : (
                                                       ) <anonymous union>
={*}

This is the output of print and display commands

(gdb) print v

$1 = std::vector of length 2, capacity 2 = {2, 3}

(gdb) print s

$2 = "HELLO WORLD"

(gdb) display s

1: s = "HELLO WORLD"

(gdb) display v

2: v = std::vector of length 2, capacity 2 = {2, 3}

(gdb)

Thanks.

[pyclewn] [ANN] pyclewn release 2.2

[Xavier de G. <xd...@gm...>]

Pyclewn 2.2 has been released at http://pyclewn.sourceforge.net/

Pyclewn is a Python program that allows the use of Vim as a front end to the GNU debugger gdb and the Python debugger pdb.

This release fixes the following bugs:

* Print the return value when the inferior stops after 'finish'.

* Fix Pyclewn failure to start when gdb is configured with ``enable-targets=all``.

* File name completion is now available before gdb has been started. This fixes a regression introduced in 2.1 by the full gdb completion feature.

* Hitting <CR> in the breakpoints window now splits the first window of the current tab loaded with a non-clewn buffer.

* Prevent pip using wheel to install pyclewn on Python 2.7.

-- 
Xavier

Les Chemins de Lokoti: http://lokoti.alwaysdata.net

[pyclewn] [ANN] pyclewn release 2.1

[Xavier de G. <xd...@gm...>]

Pyclewn 2.1 has been released at http://pyclewn.sourceforge.net/

Version 2.1 brings full gdb completion and a better handling of Vim windows.
See below for the full details.

Xavier


===============
New features
^^^^^^^^^^^^

* Full gdb completion is now available on Vim command line. See
   ``:help gdb-completion``.

* The console and the Pyclewn buffers are loaded in windows of a dedicated tab
   page when the ``--window`` option is set to ``usetab``. See
   ``help pyclewn-usetab``.

* The new command ``Cexitclewn`` closes the debugging session and removes the
   Pyclewn buffers and their windows (issue #20).

* Two new key mappings are available in the breakpoints window. Use ``+`` to
   toggle the breakpoint state between enable/disable, and use ``<C-K>`` to
   delete the breakpoint.

* The new vim.ping() function may be used to check whether an existing Python
   process may be attached to.

Changes
^^^^^^^

* Many improvements to the handling of the Pyclewn windows (issue #17).

* No windows are created when the ``--window`` option is set to ``none``.

Bug fixes
^^^^^^^^^

* Issue #6: Fix the crash in Pyclewn versions 2.0 and 2.0.1 when trying to
   attach to a remote gdb.

* Issue #12: Prevent Pyclewn from running with an obsolete version of its Vim
   run time files.

* Issue #13: Fix the error messages after ``:Pyclewn pdb`` failure.

* Issue #14: tmux can be used now with the ``terminal`` option, e.g.
   ``--terminal=tmux,split-window``.

* Issue #15: The clewn buffers are now emptied after the ``Cquit`` command.

* Issue #18: Create the windows layout upon starting Pyclewn. The windows
   layout is still created upon the first command instead, when Pyclewn is
   started with ``python -m clewn --window=usetab``.

* Issue #19: Vim signs are placed now in the window of a buffer loaded before
   the debugging session instead of using the current window.

* Issue #22: Autoscroll the console when the ``--window`` option is set to
   ``none``.

* Issue #21: A gdb error message is printed now when the ``Cdbgvar`` command
   fails.
===============

Re: [pyclewn] Crash when trying to use debug from a core file.

[Steve H. <ste...@gm...>]

That worked great, thank you!

Steve


On Fri, Mar 27, 2015 at 8:58 AM Xavier de Gaye <xd...@gm...> wrote:

> On 03/26/2015 03:48 PM, Steve Herrell wrote:
>  > I'm seeing a python back trace when I attempt to debug from a core dump
> file.
>
>
> Hi Steve,
>
> Thanks for this exhaustive report.
> The backtrace is the same as the one that occured in issue #6:
> "Pyclewn crashes when trying to attach to a remote gdb" at:
>
>    https://bitbucket.org/xdegaye/pyclewn/issue/6
>
> The cause is that the thread name is unknown to gdb both when connecting to
> the target using gdbserver or in your test case with a core file. And
> Pyclewn
> did not handle that correctly. Issue #6 has been fixed and your core file
> test
> case does not crash anymore on the current development version.
>
> The next Pyclewn version 2.1 should be released at the end of next week.
> Otherwise, you can build Pyclewn from the BitBucket repository by cloning
> it
> with:
>
>    hg clone https://xd...@bi.../xdegaye/pyclewn
>
> And reading the section named "Installing from the development version at
> BitBucket" of the INSTALL file found in the local repository that you just
> cloned.
>
>
>  > Many thanks  for a great program,
>
> Thanks, this is nice to know.
>
> Xavier
>
>

Re: [pyclewn] Crash when trying to use debug from a core file.

[Xavier de G. <xd...@gm...>]

On 03/26/2015 03:48 PM, Steve Herrell wrote:
 > I'm seeing a python back trace when I attempt to debug from a core dump file.


Hi Steve,

Thanks for this exhaustive report.
The backtrace is the same as the one that occured in issue #6:
"Pyclewn crashes when trying to attach to a remote gdb" at:

   https://bitbucket.org/xdegaye/pyclewn/issue/6

The cause is that the thread name is unknown to gdb both when connecting to
the target using gdbserver or in your test case with a core file. And Pyclewn
did not handle that correctly. Issue #6 has been fixed and your core file test
case does not crash anymore on the current development version.

The next Pyclewn version 2.1 should be released at the end of next week.
Otherwise, you can build Pyclewn from the BitBucket repository by cloning it
with:

   hg clone https://xd...@bi.../xdegaye/pyclewn

And reading the section named "Installing from the development version at
BitBucket" of the INSTALL file found in the local repository that you just
cloned.


 > Many thanks  for a great program,

Thanks, this is nice to know.

Xavier

[pyclewn] Crash when trying to use debug from a core file.

[Steve H. <ste...@gm...>]

Hi.

I'm seeing a python back trace when I attempt to debug from a core dump
file. I create a core by building and running the following code:

int main()
{
int* p = 0;
*p = 20;
}
gcc -o test test.cpp
./test

And I'm starting pyclewn with

python -m clewn -e vim -l nbdebug -f out.2
 --or--
python3 -m clewn -e vim -l nbdebug -f out.3

And run the following commands from inside vim:

  :Cfile ./test
  :C core-file core

I see a "Connection reset by peer" error flash on screen and the following
back trace is written to the log. (Note, the python3 back trace is very
similar but uses asyncio not trollius.)

<--- loads cut --->

58.538 nb   NBDEBUG +++
58.538 nb   NBDEBUG @@ -0,0 +1 @@
58.538 nb   NBDEBUG +* #0   in main
58.538 nb   NBDEBUG 3:startAtomic!53
58.538 nb   NBDEBUG 3:setReadOnly!54 F
58.538 nb   NBDEBUG 3:insert/55 0 "* #0   in main\n"
58.538 nb   NBDEBUG 3:setReadOnly!56 T
58.538 nb   NBDEBUG 5:setDot!57 1/0
58.538 nb   NBDEBUG 3:endAtomic!58
58.538 nb   NBDEBUG 4:editFile!59 "(clewn)_threads"
58.538 nb   NBDEBUG 4:setReadOnly!60 T
58.538 trol ERROR   Exception in callback _read_ready()
handle: <Handle _read_ready() created at
/usr/local/lib/python2.7/dist-packages/trollius/selector_events.py:201>
source_traceback: Object created at (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/usr/local/lib/python2.7/dist-packages/clewn/__main__.py", line 10,
in <module>
    vim.main()
  File "/usr/local/lib/python2.7/dist-packages/clewn/vim.py", line 228, in
main
    loop=vim.loop)
  File "/usr/local/lib/python2.7/dist-packages/clewn/misc.py", line 223, in
cancel_after_first_completed
    loop.run_until_complete(main_task)
  File "/usr/local/lib/python2.7/dist-packages/trollius/base_events.py",
line 288, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python2.7/dist-packages/trollius/base_events.py",
line 260, in run_forever
    self._run_once()
  File "/usr/local/lib/python2.7/dist-packages/trollius/base_events.py",
line 1116, in _run_once
    handle._run()
  File "/usr/local/lib/python2.7/dist-packages/trollius/events.py", line
151, in _run
    self._callback(*self._args)
  File "/usr/local/lib/python2.7/dist-packages/trollius/tasks.py", line
255, in _step
    result = next(coro)
  File "/usr/local/lib/python2.7/dist-packages/trollius/base_events.py",
line 638, in _create_connection_transport
    transport = self._make_socket_transport(sock, protocol, waiter)
  File
"/usr/local/lib/python2.7/dist-packages/trollius/selector_events.py", line
78, in _make_socket_transport
    extra, server)
  File
"/usr/local/lib/python2.7/dist-packages/trollius/selector_events.py", line
579, in __init__
    self._loop.add_reader(self._sock_fd, self._read_ready)
  File
"/usr/local/lib/python2.7/dist-packages/trollius/selector_events.py", line
201, in add_reader
    handle = events.Handle(callback, args, self)
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/trollius/events.py", line
151, in _run
    self._callback(*self._args)
  File
"/usr/local/lib/python2.7/dist-packages/trollius/selector_events.py", line
614, in _read_ready
    self._protocol.data_received(data)
  File "/usr/local/lib/python2.7/dist-packages/clewn/process.py", line 153,
in data_received
    misc.handle_as_lines(data, self.ibuff, self.handle_line)
  File "/usr/local/lib/python2.7/dist-packages/clewn/misc.py", line 199, in
handle_as_lines
    handle_cb(line)
  File "/usr/local/lib/python2.7/dist-packages/clewn/gdb.py", line 786, in
handle_line
    self.process_mi_record(matchobj)
  File "/usr/local/lib/python2.7/dist-packages/clewn/gdb.py", line 834, in
process_mi_record
    self.process_oob()
  File "/usr/local/lib/python2.7/dist-packages/clewn/gdb.py", line 874, in
process_oob
    self.terminate_cmd()
  File "/usr/local/lib/python2.7/dist-packages/clewn/gdb.py", line 741, in
terminate_cmd
    self.info.threads_dirty)
  File "/usr/local/lib/python2.7/dist-packages/clewn/debugger.py", line
554, in update_listbuffer
    lbuf.update(getdata())
  File "/usr/local/lib/python2.7/dist-packages/clewn/gdbmi.py", line 619,
in collect_threads
    ' %(target-id)s' % thread)
KeyError: u'name'
58.539 vim  INFO    got signal None
58.540 misc INFO    <Task finished coro=<run() done, defined at
/usr/local/lib/python2.7/dist-packages/clewn/vim.py:620> result=None
created at /usr/local/lib/python2.7/dist-packages/clewn/vim.py:226>
58.819 vim  DEBUG   Vim instance:

<--- loads cut --->

If I run the program from inside vim debugging works as expected. I can
provide the full outputs of python and python3  runs if needed.

I'm using:

pyclewn: 2.0.1
vim: 7.4
ubuntu: 14.04
gcc: 4.8.2


Many thanks  for a great program,

Steve

[pyclewn] [ANN] pyclewn release 2.0.1

[Xavier de G. <xd...@gm...>]

Pyclewn 2.0.1 has been released at http://pyclewn.sourceforge.net/

Version 2.0.1 does not require anymore a specific pdb-clone version since the
single pdb-clone source distribution is now common to all Python supported
versions.

This release also fixes the following bugs:

  The ':Pyclewn' command can now be used reliably in a Vim script.
  The watchpoints are also displayed in the breakpoints window.
  The ``Cquit`` command does not start a new gdb session anymore.
  The list buffer windows are now empty after the ``Cquit`` command.
  The source distribution can be built when pdb-clone is missing.


Xavier

[pyclewn] [ANN] Pyclewn 2.0

[Xavier de G. <xd...@gm...>]

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

[pyclewn] Moving to BitBucket

[Xavier de G. <xd...@gm...>]

The pyclewn repository and issue tracker have been moved to BitBucket at https://bitbucket.org/xdegaye/pyclewn
The web site and mailing list remain at Sourceforge.

-- Xavier

Re: [pyclewn] Balloon fails to popup sometimes

[Xavier de G. <xd...@gm...>]

On Wed, Nov 12, 2014 at 5:12 AM, Rajesh Khan wrote:
> I wanted to know if anyone has experienced this,
> I have set a couple of breakpoints and when those breakpoints hit. I point
> my mouse on a variable which is in scope and no balloon pops up thus i
> cannot know the content of that variable. /however if I quit and restart
> again. (i.e) quit gvim and from console type pyclewn. Then restart the
> process (setting up my breakpoints) I get the balloons back. Any suggestions
> on how I can fix this problem ?
>

Can you provide the steps to reproduce the problem.

--Xavier

[pyclewn] Balloon fails to popup sometimes

[Rajesh K. <raj...@gm...>]

I wanted to know if anyone has experienced this,
I have set a couple of breakpoints and when those breakpoints hit. I point
my mouse on a variable which is in scope and no balloon pops up thus i
cannot know the content of that variable. /however if I quit and restart
again. (i.e) quit gvim and from console type pyclewn. Then restart the
process (setting up my breakpoints) I get the balloons back. Any
suggestions on how I can fix this problem ?

Re: [pyclewn] How to get a stack trace when debugging

[Xavier de G. <xd...@gm...>]

See https://sourceware.org/gdb/current/onlinedocs/gdb/Stack.html#Stack

--Xavier

[pyclewn] How to get a stack trace when debugging

[Rajesh K. <raj...@gm...>]

I wanted to know how I can get a stack trace at a certain breakpoint.
I know how to set a breakpoint. What i want is a way to see the stacktrace.
I tried doing Cthreadstack but it says the command is not an editor command