Forum > Lazarus

Lazarus Release 2.2.2

<< < (11/12) > >>

jipété:

--- Quote from: Handoko on June 20, 2022, 07:19:58 am ---I confirm what RadDeveloper said is reproducible on Lazarus 2.2.2 Linux GTK2.

--- End quote ---
Also in old 2.2.0.

RadDeveloper:

--- Quote from: dseligo on June 21, 2022, 10:33:55 am ---
--- Quote from: RadDeveloper on June 21, 2022, 07:36:47 am ---Cannot Debug Win32/Release Application in Lazarus IDE

--- End quote ---

Is your Lazarus installation 64 bit or 32 bit?
What debugger you use, FpDebug or GDB (Project/Project options/Project options/Debugger)?

--- End quote ---
Thank you for the reply.
GNU debugger(dbg.exe) falls in the error above I mentioned.
So workaround:
Replace the path with the placeholders e.g
..\Lazarus\mingw\i386-win32\bin\gdb.exe
to
$(LazarusDir)\mingw\$(TargetCPU)-$(TargetOS)\bin\gdb.exe

Now it's working :-)

dseligo:

--- Quote from: RadDeveloper on June 21, 2022, 10:05:07 pm ---
--- Quote from: dseligo on June 21, 2022, 10:33:55 am ---
--- Quote from: RadDeveloper on June 21, 2022, 07:36:47 am ---Cannot Debug Win32/Release Application in Lazarus IDE

--- End quote ---

Is your Lazarus installation 64 bit or 32 bit?
What debugger you use, FpDebug or GDB (Project/Project options/Project options/Debugger)?

--- End quote ---
Thank you for the reply.
GNU debugger(dbg.exe) falls in the error above I mentioned.

--- End quote ---

You probably don't have 32-bit gdb installed (under Lazarus install directory\mingw, 32-bit in i386-win32\bin\gdb.exe and 64-bit in x86_64-win64\bin\gdb.exe).

Martin_fr:
Or your app depends on some dll, that you did not put in the new install?


--- Quote ---Execution stopped with exit-code
--- End quote ---
This usually means that your app was started [(1)] (and for that you must have some debugger (if your setting is gdb, then some gdb.exe)), and your app did then quit

[(1)] The exe file was opened by the OS, but it may (or may not) have failed before any code was executed.

- This could be, that the IDE config is hard coded to the 64 bit debugger (though IIRC that causes a diff error).

- Or it could be, that the OS failed to load dependencies.

- Or it could be that your Anti-Virus killed the process.

RadDeveloper:

--- Quote from: dseligo on June 21, 2022, 10:16:05 pm ---
--- Quote from: RadDeveloper on June 21, 2022, 10:05:07 pm ---
--- Quote from: dseligo on June 21, 2022, 10:33:55 am ---
--- Quote from: RadDeveloper on June 21, 2022, 07:36:47 am ---Cannot Debug Win32/Release Application in Lazarus IDE

--- End quote ---

Is your Lazarus installation 64 bit or 32 bit?
What debugger you use, FpDebug or GDB (Project/Project options/Project options/Debugger)?

--- End quote ---
Thank you for the reply.
GNU debugger(dbg.exe) falls in the error above I mentioned.

--- End quote ---

You probably don't have 32-bit gdb installed (under Lazarus install directory\mingw, 32-bit in i386-win32\bin\gdb.exe and 64-bit in x86_64-win64\bin\gdb.exe).

--- End quote ---
Yes I do have 64-bit installed on Windows, plus FPC addon. Seems like correct path with placeholders included were not edited since out of box installation, so I had to put them manually.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version