What steps will reproduce the problem? 1. Install pydbgr 2. Start pydbgr 3. Press return twice

What is the expected output? What do you see instead?

Expected blank new lines. This is what I got:

(Pydbgr) Traceback (most recent call last): File "/usr/bin/pydbgr", line 9, in <module> load_entry_point('pydbgr==0.1.2', 'console_scripts', 'pydbgr')() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/cli.py", line 339, in main dbg.core.processor.process_commands() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py", line 572, in process_commands leave_loop = self.process_command() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py", line 611, in process_command if last_command[0] == '#': TypeError: 'NoneType' object is unsubscriptable Uncaught exception. Entering post-mortem debugger... (/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py:611): process_command !! 611 if last_command[0] == '#': (Pydbgr:pm) Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/post_mortem.py", line 67, in post_mortem_excepthook post_mortem((exc_type, exc_value, exc_tb)) File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/post_mortem.py", line 142, in post_mortem dbg.core.processor.event_processor(f, 'exception', exc, 'Pydbgr:pm') File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py", line 310, in event_processor self.process_commands() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py", line 572, in process_commands leave_loop = self.process_command() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py", line 611, in process_command if last_command[0] == '#': TypeError: 'NoneType' object is unsubscriptable

Original exception was: Traceback (most recent call last): File "/usr/bin/pydbgr", line 9, in <module> load_entry_point('pydbgr==0.1.2', 'console_scripts', 'pydbgr')() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/cli.py", line 339, in main dbg.core.processor.process_commands() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py", line 572, in process_commands leave_loop = self.process_command() File "/usr/lib/python2.6/site-packages/pydbgr-0.1.2- py2.6.egg/pydbgr/processor/cmdproc.py", line 611, in process_command if last_command[0] == '#': TypeError: 'NoneType' object is unsubscriptable

What version of the product are you using? On what operating system?

pydbgr --version gives: pydbgr version 0.1.0

I'm using Arch Linux, fully updated, on a 64-bit computer. My version of Python is: Python 2.6.4

Please provide any additional information below. I understand that pydbgr is under heavy development.

Thanks for the report.

This problem and a couple of other problems related to running pydbgr without a script name should be fixed in svn.

Is running a debugger without a script name is something that is normally done? I've always thought of it as a little bit of an edge-case which is one reason support for it is a little bit flaky.