Debugging going on auto in 1.24

[mmtbb]

Perhaps there is a setting I am unaware of in 1.24, but if I debug and press STEP OVER or STEP INTO, it starts to automatically go from line to line, instead of stopping at each new line.

[pvs]

Too bad. I was hoping this would've been fixed in 1.24. I saw this behavior in 1.23, too.

I'm sure it will be fixed eventually. As a rusty old programmer, I make extensive use of the debugger, and need it to work.

Hopefully, 1.25 will see it repaired.

Best regards, all, and a happy holiday to anyone celebrating.

-pvs

[SJD]

Guys, I'm confused. Both - "Step Over" and "Step Into" stopping me normaly at each new line. I have other problem with them - both behave in the same way - as "Step Into", in my opinion. I tested it in 1.23/1.24

Jerry
-------------------------
PPLG (PPL is Great)


Ooops - it works good, I'm stupid :-)

[SJD]

I have a mad idea - don't you forget to locate there any break-point?

Jerry
-------------------------
PPLG (PPL is Great)

[pvs]

SJD ... I must admit, I have not had a chance to test 1.24 yet. I only responded after seeing MMTBB's comment, and knew my experience with 1.23.

But in 1.23, yes, of course I had set breakpoints ... but the debugger would not stop at any except the first one, and from there, would trace through the program, ignoring any subsequent breaks.

I will try to test 1.24 out later today or tomorrow, and report back here with my finding.

-pvs

[SJD]

Hi Paul,
I checked it again - in 1.23 only (1.24 I deinstalled for the present)
I state that it works fine - both - from PIDE at PC and at PPC also :?
I tempted to find some strange settings (options) - but nothing...

Jerry
--------------------------
PPLG (PPL is Great)

[mmtbb]

Hi Kornalius, there is definetely a problem here. I reinstalled 1.24 completely clean. I open any file. Run it in debug mode with a breakpoint. When that breakpoint is triggered, the program stops. Just like PVS stated, by pushing Step Over, OR Step Into, the program will then trace non-stop through the rest of the program commands.

I'm sure it is a simple fix.
If any of you are experiencing this too, and really need the debug feature, I know 1.21 does not have this bug. Perhaps other builds are safe as well.

Cheers,
John

[kornalius]

Sorry about this guys, I have done extensive tests in 1.24 to make sure it would work. I will need to get back to it again and make sure it works again in 1.25 which I expect to release early next week so I can move on to the new features for version 1.30.

[SJD]

Is it possible that it make any difference when I'm using PPC2002 operating system on my iPaq? Because it works good for me.

Jerry
--------------------------
PPLG (PPL is Great)[br]../../e107_files/public/1176043238_282_FT4510_ppc2.gif

[pvs]

Thanks everyone for your input on this. I DID just check 1.24 out on my desktop, and yes (unfortunately), it DOES still exhibit the "trace" behavior. I will wait for 1.25 ... patiently :)

I DO love PPL, and the capabilities it's giving me. And I thank Kornalius, and everyone else who is working to develop this product. Kudos to you all!

Hope everyone is having a nice Holiday,
-pvs

[kornalius]

Thanks pvs, we are dedicated to make this product the perfect solution for everyone.

SJD: You are still using 1.23 right? Because that white menu bar is pointing to an older version of PPL.

[SJD]

Yes, I returned back to older version for a while, so that to try this "case" :)

Jerry
-------------------------
PPLG (PPL is Great)

[kornalius]

I am currently investigating this bug, quick question, do you guys use forms to test with?

[pvs]

Mine does not, Alain. Mine are just two simple (very small apps) that copy some files around. (just starting with basics here). If you want, I could email you the code ...it's not very much at all.

Thanks for spending the time to try to solve this thing, sir.
-pvs

[kornalius]

Yes please, send them to me.

[pvs]

They're on the way via email, Alain. You should have them by now.

Good luck!
-pvs