I've installed Lazarus 0.9.28 (with FPC 2.2.4) 64 bit on Win7/64. Here gdb works.

Then I built and installed FPC 2.5 (trunk) for further use. The compiled apps (64 bit) run fine, as long as I disable debugging. With debugging enabled the application hangs on start, i.e. even the console does not appear for a console app (hello world...).

What might be wrong? Do I need a newer gdb.exe for 2.5?

DoDi

What if you run a gdb from the command line ?

Does the debuggeroutput window show something ?

Marc

See comment 0035256 at http://bugs.freepascal.org/view.php?id=15692 for how to fix it. I think the default image base for Win64 should be reduced back to something < 32 bit until this problem is solved, but the Win64 maintainers don't agree (http://bugs.freepascal.org/view.php?id=15692).

Jonas

What if you run a gdb from the command line ?

I'm somewhat confused. There seem to exist two gdb.exe on my system, with slightly different version numbers, but I can locate only one. Typically Windows - protect the system from the user :-(

After some tries: found the other (32 bit?) gdb, and renamed it. Also removed the path to FPC 2.4.0 (32 bit).

Does the debuggeroutput window show something ?

Now gdb allows to run the test program, where the other gdb (32 bit) couldn't identify the file format (64 bit).

Nonetheless when I run the same program from the Lazarus IDE, no console window opens :-(

Seems to become a Lazarus problem...

DoDi

See comment 0035256 at http://bugs.freepascal.org/view.php?id=15692 for how to fix it.

This was not the problem, but reading helped - I had to enable creation of gdb debug info, to make the debugger work with Lazarus. I wonder why gdb doesn't report any errors, when running it with the same exe without debug information created? Or is the debug info essential for Lazarus?

DoDi

make sure you use only mingw based gdb for lazarus and not a cygwin based (cygwin has a console which doesn't use stdin/out)

You cannot debug console apps in lazarus.

Marc

AFAIK it doesn't ruiquire debuginfo to be present, however without info you only can run your app.

Marc

> Nonetheless when I run the same program from the Lazarus IDE, no console > window opens :-( You cannot debug console apps in lazarus.

I can, on Windows. And, as I've just learned in the chat, it's also possible do debug console applications on Linux, at least as long as no console input is required. For that purpose Lazarus has to be started from a console, which then will receive all output, from Lazarus, debugger and debugged application. A bit weird, but at least I now can single step also on Linux :-)

After some more assistance I could make at least 32 bit console apps work with the 32 bit debugger on Win7/64. I wonder what's the problem with the 64 bit gdb. Both say they are mingw apps, and the 64 bit debugger also works with Lazarus 0.9.28 and fpc 2.2.4, but not with 2.4 or 2.5 :-(

DoDi

In our previous episode, Hans-Peter Diettrich said:

I'm somewhat confused. There seem to exist two gdb.exe on my system, with slightly different version numbers, but I can locate only one. Typically Windows - protect the system from the user :-(

Get which.cmd from http://www.robvanderwoude.com/which.php

and then use which gdb.exe to see which one it finds.