[Eric] Debugger problem

[Detlev Offenbach]

Hi,

maybe I did something wrong in order to reproduce the problem. Here is what I 
did.

Test 1:
1. open both files in eric4
2. set a breakpoint at line 3 of apackage.py
3. switch to aCallingfile.py (seems to be the main file)
4. press F5
5. execution stops at breakpoint

Test 2:
1. open both files in eric4
2. set a breakpoint at line 3 of apackage.py
3. switch to aCallingfile.py (seems to be the main file)
4. set a breakpoint at line 3 of aCallingfile.py
5. press F5
6. execution stops at breakpoint in aCallingfile.py
7. press F6 (continue)
8. execution stops at breakpoint in apackage.py
9. press F6 (continue)
10. script exits correctly

Regards,
Detlev

On Donnerstag, 21. Mai 2009, Krishna Sandeep Reddy wrote:
> I also have the same problem. It won't stop at the break point. It says
> "aCallingfile.py" script terminated with an exit status of 0.
> I have to do a single step to force the debugger go into it.
> I also tried multithreaded option, but no use.
>
>
> Cheers,
> dksr
>
> On Thu, May 21, 2009 at 10:21 AM, Detlev Offenbach
> <detlev at die-offenbachs.de
>
> > wrote:
> >
> > On Mittwoch, 20. Mai 2009, Jochen Deibele wrote:
> > > Hi!
> > >
> > > Am Mittwoch, 20. Mai 2009 19:19:57 schrieb Detlev Offenbach:
> > > > On Mittwoch, 20. Mai 2009, Jochen Deibele wrote:
> > > > > I have to files one defining a class (apackage.py) and another
> > > > > instantiating that class (aCallingfile.py). I put a breakpoint in
> > > > > apackage.py (line 3), debug the script (F5) and the breakpoint
> > > > > works.
> >
> > I
> >
> > > > > put a breakpoint in a method of the class (line 3) call the method
> >
> > from
> >
> > > > > aCallingfile, debug the script (F5) but the breakpoint is ignored.
> > > > > Am
> >
> > I
> >
> > > > > doing something wrong?
> > > > > I attached a testcase.
> > > > >
> > > > > I have also two files in a project and try debugging the project
> > > > > with the same strange behaviour.
> > > > >
> > > > > I'm using eric 4.3.3 on linux.
> > > > >
> > > > > Does anybody experience the same? Any help is appreciated!
> > > >
> > > > Works for me.
> > >
> > > Well, sadly definitly still not for me.
> > >
> > > If it was unclear above: I want to break in a method of the class if I
> > > debug the aCallingfile.py.
> > > If I put a breakpoint in the class method in apackage.py and then start
> > > debugging aCallingfile it
> > > is happily executed, the output string is written to the prompt and I
> > > get
> >
> > a
> >
> > > message that the script has finished with status 0 - but it doesn't
> >
> > break.
> >
> > > What could be wrong? Are there some preferences which I could try?
> >
> > There are no preferences that affect the breakpoint behavior. At the
> > moment I
> > have no clue about what could be wrong. As I already said, it works for
> > me over here. This means, that I am not in a position to trace the
> > problem.
> >
> > Has anybody else observed this behavior?
> >
> > Regards
> > Detlev
> > --
> > Detlev Offenbach
> > detlev at die-offenbachs.de
> > _______________________________________________
> > Eric mailing list
> > Eric at riverbankcomputing.com
> > http://www.riverbankcomputing.com/mailman/listinfo/eric



-- 
Detlev Offenbach
detlev at die-offenbachs.de