On 09/08/2012 22:02, Marc Santhoff wrote:
after having moved from a 32 bit machine to a 64 bit one I'm
experiencing a problem. I cannot start any program. I think it had been
working a while ago, but now any time a program in lazarus is started a
dialog pops up saying:
....
[Debugger] Running GDB version: 6.1.1 [FreeBSD]
That is very old... yet, it may not be the problem
Yet I have (on windows) still some success using gdb 5.2
[TDebugger.SetFileName] "/home/marc/program/Test_lazarus/LazThreads/ThrdDemo"
[Debugger] Log output: &"info file\n"
[Debugger] File type: elf64-x86-64-freebsd
[Debugger] Entry point: $447040
[WARNING] [Debugger.TargetInfo] Unknown FileType: elf64-x86-64-freebsd, using
GDB cpu
[WARNING] [Debugger] Unknown target CPU: amd64
The IDE indeed has a problem with "elf64-x86-64-freebsd ", it only knows
"elf64-x86-64". The suffix throws the IDE off.
Yet that again should not lead to an error. It may however stop the IDE
from getting exception class/message and other details...
[Debugger] Log output: &"info pid\n"
[Debugger] Log output: &"Undefined info command: \"pid\". Try \"help info\".\n"
TGDBMIDebugger.ProcessResult Error: ,msg="Undefined info command: \"pid\". Try \"help
info\"."
Might be the old gdb. But again should be recovered. This is one of
several attempts of the IDE to get the PID. Not sure if all others
failed too. If so, then that could have caused the error.
There is a possibility that your GDB is localized. In that case the IDE
can not understand all the replies...
I need a more complete log.
Please start the IDE with
| --debug-log=/home/yourname/laz.log
--debug-enable=DBG_CMD_ECHO,DBG_STATE,DBG_DATA_MONITORS,DBGMI_QUEUE_DEBUG,DBGMI_TYPE_INFO,DBG_WARNINGS
And supply the new log file
|
---------------
In the mean time in the debugger options, there is "InternalStartBreak",
you may try other values. But I can not tell, if it will help...
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus