TOPIC:

Thank you very much and congratulations CT team, this version it has worked great in Linux Mint Xfce 32-bit.

I liked the new splash.

Crossbuild for ARM and Windows is OK

regards

Thank you very much CT team, excellent, I'm impressed!
Best regards!
p.s. openSuSe12.3 32 and win7 ultimate 32

I have strange issue with debuging. Step Over (F8) is working strange. On ordinal types it working fine, but when I want step over some object property etc. I get assembler window and press F8 sill stay on this line. For example:
1. Drop button and combobox on form
2. Set some items into combo items property.
3. Add button OnClick method with folowing code:4. Set breakpoint on first line and run application.
5. Click on button, F8 works on "i := ..." lines but on Button1.Caption some strange behavior occur

CT 4.20
Linux Mint 14 64bit, XFCE (GTK)

Thanks guys
have fun...

dibo wrote: I have strange issue with debuging. Step Over (F8) is working strange. On ordinal types it working fine, but when I want step over some object property etc. I get assembler window and press F8 sill stay on this line. For example:
1. Drop button and combobox on form
2. Set some items into combo items property.
3. Add button OnClick method with folowing code:

procedure TForm1.Button1Click(Sender: TObject);
var i: Integer;
begin
  i := 1;
  i := 2;
  i := 3;
  Button1.Caption := ComboBox1.Items.Strings[ComboBox1.ItemIndex];
  i := 4;
  i := 5;
  i := 6;
end;

4. Set breakpoint on first line and run application.
5. Click on button, F8 works on "i := ..." lines but on Button1.Caption some strange behavior occur

CT 4.20
Linux Mint 14 64bit, XFCE (GTK)

We will check this Sir

sternas wrote: We will check this Sir

I got back to the CT 4.10 and debugging is working fine now

dibo wrote: I got back to the CT 4.10 and debugging is working fine now

Have you tried to replace GDB.EXE in 4.20 with GDB.EXE from 4.10? There were debugging issues in the past that were solved in a similar way, and it was new GDB version fault.

My suggestion,
try to use type of Debug info: Stabs (-gs)
in your Project debug options

avra wrote:

dibo wrote: I got back to the CT 4.10 and debugging is working fine now

Have you tried to replace GDB.EXE in 4.20 with GDB.EXE from 4.10? There were debugging issues in the past that were solved in a similar way, and it was new GDB version fault.

I have linux mint, practically from today - Xubuntu (debian distro also). Seems that CT doesn't ships own GDB but using system GDB (debugger path in lazarus options point to /usr/bin/gdb). So I supose that both 4.10 and 4.20 usign same GDB but 4.20 has some bad Lazarus/FPC svn revision

My suggestion,
try to use type of Debug info: Stabs (-gs)
in your Project debug options

Doesn't help

Sir
on Linux/Unix OSes CT use system GDB
on Windows, we include with CT our GDB SVN builds (7.5.50 SVN 12-9-2012)

So give us more info:
-Your GDB version, on your Linux Box?
-Which Linux Mint or Xubuntu Version?
-Your Linux Box have Custom structure?
-etc

Xubuntu 12.10 64bit (but same error on Linux Mint 14 64bit XFCE)

From Xubuntu:

Not here, it does not. Windows 7 ultimate. With version 4.1, I could click on the 'Lazarus' icon and Lazarus would load and work OK. When I do the same with version 4.2, nothing happens. I installed it exactly in accordance to the instructions. I have tried with Lazarus bigIDE and Lazarus small ide. The examples in the help file are still the same time-expired wrong and unhelpful information. Having spent many frustrating hours trying and failing to make CodeTyphon work, more in sorrow than in anger, I'm off to delete codetyphon and reinstall stand-alone Lazarus until the codetyphon writers are able and willing to bring their obviously considerable efforts to a properly stable working state and provide the proper 'help' files, support, and 'HowTo' documentation that are currently almost totally missing.