Skip to content

some bug #24

Open
Open

Description

@chp845

python debug:

  1. when i quit the debug , the pydbpg is still runing int the back
  2. when i step in a liabray(egg or zip format), the vim can't show the file and also can't debug the file

Activity

  1. jaredly commented on Dec 10, 2013

    @jaredly
    Owner

    Hmmm stepping into a zip file is an interesting issue. I guess we could unzip & open the tmp file -- it would take some juggling, but it's doable.

    As for 1, I have an idea as to how to fix it

  2. shmup commented on Mar 20, 2014

    @shmup

    My bug might be related to chp845's first one.

    1. open vim, open foo.py, Dbg .
    2. I do things within vim-debug, breakpoints, etc, all is well

    3a. :Dbg quit WORKS, great. It leaves, and I can start debugging again later just fine.

    3b. :Dbg stop takes me out of the debugging UI, but I cannot start again. It just shows the list of commands. You would think this means I have to still :Dbg quit, but if I do I receive:

    Error detected while processing : Traceback (most recent call last): File "<string>", line 1, in <module> File "/usr/local/lib/python2.7/dist-packages/vim_debug/commands.py", line 44, in debugger_cmd cmd['function'](*args) File "/usr/local/lib/python2.7/dist-packages/vim_debug/new_debugger.py", line 177, in quit vim_quit() File "/usr/local/lib/python2.7/dist-packages/vim_debug/new_debugger.py", line 17, in vim_quit vim.command('cuna dbg') vim.error: Vim(cunabbrev):E24: No such abbreviation

    3c. :Dbg exit -- same as 3b

    For 3b and 3c, I just quit vim and open again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions