I need a REAL debugger!


#1

It’s shameful that Clarion doesn’t have a decent debugger.
It lacks basic features like the ability to see the value of an ANY variable !
Let alone all the WYSIWYG features that you can find in other professional products.
I can’t save breakpoints, I can’t have conditional breakpoints, I have to search for the variable I’m looking for in the right procedure or module. I need a lot of time only to setup a debugging session.
It can’t be that hard to add these features but if they don’t think a debugger is important why don’t they release the source code for us to modify it ?


#2

I hear ya!

If they do that I think we have some good options. I encourage you to reach out to SV directly and make it known how important this is. Honestly I think they don’t know.


#3

Hey Brahn!
I wrote on the sv.clarion.clarion10 newsgroup in March 2015.
This is the R. Zaunere reply:


Alberto,

“Work is being done on the debug info that is generated, so that
eventually you can use other debuggers (e.g. Visual Studio debugger)
with your Clarion apps.”.
This was a good news in my opinion.

To get to that point requires a fundamental change in the Obj format - we’re
intending to make it there but its not a small short-term change.

Robert


#4

Ouch, that doesn’t age well does it. I mean, I guess it just hasn’t bubbled up the priority list or something but hmmph! I use the debugger quite often but each time it is a pain.

I bumped the thread in the newsgroup.


#5

As with all things SV, believe it when you see it. The resources are just not available for making significant changes in a timely manner.


#6

And I replied to your bump.

I agree. So I proposed to release the debugger to the community. They’ll never do it, but it’s worth trying


#7

Just read what Zaunere replied… no hope for the next three years to say the least, but I would do a conspicuous bet on five years.
And obviously no reply to my foolish idea of releasing the source code of the current debugger.


#8

I use UltimateDebug and send debugging info out the standard DebugView from SysInternals.
Include their clw in each app, then I declare a new class in the procedure I want to debug.
By using the property DebugOff, you can turn it on/off as needed so once you setup a procedure it can be turned off for production and if there is a problem just turn it on recompile and you’re good to go.
There is a bit of setup time, but once a procedure is ‘debugged’ via code, all you have to do is turn it on and you have detailed debugging on what you want to see.


#9

DebugView is useful to debug in certain situations and I’ve succesfully used it.
In normal situations the Clarion debugger is more flexible, but still nowhere near to a modern debugger.
Visual Studio has had a modern debugger since about 1997 … 20 years …