[Eric] Shell and Breaking on Exception

[Detlev Offenbach]

Hello Mark,

thanks for being so patient and helping to debug the issue. The 
observation is caused by a forgotten line of code. The locals dict of the 
current frame was not remembered in case of an exception. That is fixed in 
the current sources. The change will be part of the next release. If you 
need it urgently, just copy it over from the sources. Sources are available 
via the source code repository. See the eric web site for details.

Regards,
Detlev

On Monday 06 May 2013, 12:57:07 Mark Mordeca wrote:


Hi,
 
I’m sorry to bring this up again, but I did more troubleshooting into what is 
causing my problem and have narrowed it down to a difference in eric4 
versions.  Up to version 4.4.12 (r3937), eric4 behaves as I expect; i.e. 
when I run with F2 (or shift+F2) and an exception occurs, I say yes to if I 
would like to break at the exception, and then in the shell I can type “self” 
and variable names to access the variables in the memory space.  When I 
upgrade to the next version in line, 4.4.13 (r3989), this no longer works – 
when I say yes to break at the exception and type self (or other variables 
that do exist) in the shell, I get not defined errors.
 
The change log is unhelpful, the entry for 4.4.13 is “bug fixes”.  Can you 
please provide any insight into what changed in between these two 
versions that could cause this?
 
Thank you,
Mark
 
*From:* Detlev Offenbach [mailto:detlev at die-offenbachs.de[1]] 

*Sent:* April-24-13 12:08 PM

*To:* eric at riverbankcomputing.com[2]
*Cc:* Mark Mordeca

*Subject:* Re: [Eric] Shell and Breaking on Exception
 
There was nothing removed in this area and it works over here.

On Wednesday 24 April 2013, 11:05:56 Mark Mordeca wrote:
Greetings,
 
I have recently upgraded my version of Qt/PyQt and so have upgraded my 
version of Eric4 to the latest one.  In the previous version of Eric I was 
using (4.3.10), when an exception occurred and the dialog appeared, I 
would choose to break at it and then I would be able to use the shell to 
interact with variables in the memory space.  After upgrading to latest 
version I cannot interact with the variables when choosing to break at an 
exception anymore and so now when an exception occurs I have to choose 
to break at it, explicitly place a break point at that spot and then re-run in 
debug mode.
 
Was the functionality that occurred in the old version removed or made as 
some setting that is defaulted to off now?  Or is there something weird in 
my new setup that causes this? Any help would be appreciated.
 
Thanks,
Mark 
 


*Detlev Offenbach*
detlev at die-offenbachs.de[1]


*Detlev Offenbach*
detlev at die-offenbachs.de

--------
[1] mailto:detlev at die-offenbachs.de
[2] mailto:eric at riverbankcomputing.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.riverbankcomputing.com/pipermail/eric/attachments/20130506/9df369f5/attachment-0001.html>