TOPIC:

my projects all are running with this lab without any problem until now.
Great work again!

Thanks Sir

-On Windows Typhon IDE buttons now have icons like GTK2, QT4, QT5 and Cocoa.

- New IDE form, Typhon IDE => View => IDE Property Editors
you can Enabled/Disabled IDE Property Editors

-lz_FpWeb has 3 new comp for REST
TSQLDBRESTDispatcher,
TSQLDBRESTSchema,
TRESTBasicAuthenticator
and before 30 min we add and TSQLDBRestBusinessProcessor more info

-Fixes for all Debuggers

- etc, etc, etc, etc

PS:From previews CT revision 006710 this CT revision 006720
has 10 pages of updates

Thank You,
some things I found in meantime - cool !

and
-I don't write anything for the updates in
Pas2js FreePascal Technology.
Server side or Client side,
Web Applications and Web Database Applications from any CT Host OS.

-Did you try to build Pas2js App with Latest LAB CT 6.80 rev 006720 on latest Solaris or on latest OpenIndiana OS ?.

-I don't write anything for the updates in pl_OpenGL more info here

-I don't write anything for the updates in pl_Vulkan more info here
and how these updates work on the latest Fedora 29 Linux the only Linux Distribution (until now) with support to Vulkan API by MESA Drivers.

- etc, etc, etc, etc,

CodeTyphon "Programming Cosmos" it's BIG very BIG

Hello,
is it possible to make CT installation path with version? For example instead of c:\codetyphon , c:\codetyphon_6.8, so that we could install and test multiple versions at same time. And then we just have to use --pcp argument to point to the settings folder (--pcp=C:\Users\user\AppData\Roaming\typhon32_6.8).
Thanks.

No Sir
this is NOT possible

I have a problem with debugging and CT6.8 and CT 6.81.
The Problem is on two computers one with Win7 32 Bit and one with Win10 64 Bit.
It appears with both CT 32 Bit and CT 64 bit with GDB.

It appears randomly on a day by day basis.
If it has happened once, then it happens again and again, and if it has not happened then this is persistent until the next boot.

The problem: If I set a breakpoint in the example code below, then it is not hit. If this happens, singlestepping is not possible and I must reset the debugger.

This type of random behavior is typical for uninitialized variables or buffer overflow somewhere, but that is only my educated guess.

There is another different problem since previous CT versions, I dont know which:

It is not possible to step into FormatDateTime and other routines that are located in "dati.inc".
If I set a breakpoint in dati.inc it is not hit.
This problem is not random it is reproducible 100%.
I do not know if this is a bug, or if this is intentional.
(I am not coming from Delphi and I am new to Object Pascal. So I use the debugger a lot, not to debug, but to explore this stuff and to learn how all this works and how it fits together.)

Sir
did you try FpDebugger ?

Yes.

FPdebugger does not step into FormatDateTime.

So far I remember, it hits the breakpoints, but I am not very sure because the problem is random.
Sometimes the problem vanishes when I compile with zero optimization and sometimes not.

Yesterday I upgraded to CT6.81 here on this computer (Win7 32 Bit)
Now I wanted to try again with FpDebug but it does not appear on the list..

I use the medium sized IDE here, because the big IDE is not built with only 4Gb of RAM.
(I have the WIN7 3GB switch enabled, so I have virtually 3 GB of user adress-space and 1 GB of kernel adress-space)

just install to the IDE
lz_debuggerfp package for FpDebugger and
lz_debuggerlldb package for LLDB debugger.

FpDebugger is ok now.
It stops at a breakpoint.
However, currently also GDB stops at the breakpoint. (I am referring to the simple test project above.) So I have to try again, when the problem occurs again. I dont know a way to force it, it happens randomly.

Both debuggers do not step into FormatDateTime.

lz_debuggerlldb was already installed.
If I try it, I get a message about a missing DLL.

My mistake

CT version of LLDB don't support Win7

I found a way to trigger the problem:

I open my testproject, that has a breakpoint set and start a debug session.
The breakpoint is hit.

I open another small project, (multithreadingexample1 from CodeOcean) that has a breakpoint set and start the debug session. The problem happens, the breakpoint is not hit and the following behaviour is strange.
I open my testproject again.
The breakpoint is not hit and the behaviour is strange.

This happens with both, GDB and FpDebug.
In the case of FpDebug I get an access violation instead of strange behaviour.
I dont know if this is the only way to trigger the problem, an if this is 100% reproducible, but I did this several times and got the problem.

Here a screenshot with FpDebug:




I found another little bug, that is independent:
If I try to run a program without debug (Ctrl-Shift-F9) nothing happens, it doesnt start.

If I press CTRL-Shift-F9 on Linux the Project will be compiled and linked but did not start automaticaly

(Probably) the same as on Windows.
If the source was modified, Ctrl Shift F9 compiles and builds the project, but does not start the executable.
If the source was not modified, nothing happens.
"Build" and "Compile" both do the same, they build the project unconditionally independent from source modification.
There is nothing different when the toolbar, the menu or keyboard shortcuts are used.

Guys
we are working on this...

We release LAB CodeTyphon ver 6.80 Revision 006730

Please, test, report and
have fun....

When I try to find the procedure definition of any procedure in datih.inc, then I get this message in the message window:

CTLAB 6.8 32 Bit medium sized IDE on Win7 32 Bit

Edit:
I added a screenshot with another example:
If I use Alt-Up to go from my project to the unit SysUtils I get:

Just restart the Typhon IDE and try again

IDE CodeTools need more work...