Re: [Boa Constr] Debugger startup error message

[Riaan B. <riaan@e.co.za>]

Hi Frans,

F.A. Pinkse wrote:
> Hi All,
> 
> 
> Whenever I start the Debugger with this sequnce:
> In the Editor Tool button Debugger application [ the Red one ]
> followed by the Debugger tool button Out-F6 [ curved up Arrow ]
> I get This error message.
> 
> 
> Traceback (most recent call last):
>    File 
> "C:\Python25\Lib\site-packages\boa\Debugger\IsolatedDebugger.py", line 
> 348, in execute
>      result = getattr(ob, self.func_name)(*self.args, **self.kw)
>    File 
> "C:\Python25\Lib\site-packages\boa\Debugger\IsolatedDebugger.py", line 
> 867, in set_step_out
>      raise DebugError('No current frame')
> DebugError: No current frame
> 
> When I do a double click on the Editor tool button Debugger no such 
> message appears.
> 
> Is this a real error or is my way of operating flawed.

I can't reproduce this problem.

I've tried various variations on these steps:
* Open a module (standalone or application)
* Click Debug on the Editor toolbar (Debugger window opens)
* Click Out on the Debugger toolbar (program runs under debugger)

This works for me on all the modules/applications I tested.

Does this happen for you on a specific program or any module you debug?

PS, in principal this way is not flawed but it's not that useful either,
it implies that the debugger should break after it returns from the top
most entry point (IOW after program completion) where it exits anyway.
So it should behave the same as Debug (F4) in principal.

I'm very curious what you do differently that causes this exception.

Thanks,
Riaan.