Your first log showed that your project was compiled for x86.
What CPU do you have?
Intel X86, M1 or M2?
Typing
lldb --version
into a terminal, which version is reported?
I provided the debug output
See above
Ah, sorry. Possible that 2.2.6 has a different output from what I expected (and hence I thought it was from a different log / the debugger can log similar info to different outputs).
I expected something like (note the ">>" on many of the lines / but that may be 3.0 only)
(lldb) breakpoint set --func fpc_runerror -K false
Breakpoint 2: no locations (pending).
>> breakpoint set --func fpc_raiseexception -K false
WARNING: Unable to resolve breakpoint to any actual locations.
(lldb) breakpoint set --func fpc_raiseexception -K false
Breakpoint 3: where = project1`FPC_RAISEEXCEPTION, address = 0x0000000000433340
>> breakpoint command add 3
>> p/x $rdi
>> p/x $rdx
>> p ((char ***)$rdi)[0][3]
>> p ((char **)$rdi)[1]
>> DONE
>> version
(lldb) breakpoint command add 3
(lldb) version
>> breakpoint command add 2
>> p/x $rdi
>> DONE
>> version
lldb version 16.0.6
(lldb) breakpoint command add 2
(lldb) version
>> breakpoint command add 1
>> p/x $rdi
>> DONE
>> version
lldb version 16.0.6
(lldb) breakpoint command add 1
(lldb) version
>> process launch -n
lldb version 16.0.6
(lldb) process launch -n
Process 2990 launched: '/home/m/tmp/project1' (x86_64)
It is always hard to analyse output of an older version.
Yours also misses the "breakpoint command add 3" which should be there even in the old IDE.
So in any case, your first post had output that contained "Process 3151 launched: ....."
Which means if you press pause, the "debug output" should print "process interrupt". And hopefully pause the app.
Your later post does not contain that. Which means something unexpected with lldb itself. Maybe a different lldb version. Some people reported issues (
albeit different from yours) with the latest xcode (and the lldb that comes with it)
Unfortunately from here on forward, it all becomes a bit guess work.
On Mac debugging needs lldb, which is not under our control, and so if it does not behave, it can be a lot of guessing to try and find out more...
The missing "Process.. launched:" in the 2nd example may be a serious issue. If the log did not omit anything then that may be a bug in lldb which may not be easy to workaround (if at all)
The absence of the "breakpoint command add 3" is puzzling though, since this should be added by the IDE and the output up to the point were it should be looks correct. That makes me think, that there may be something missing from the logs.
Since nothing will be fixed on 2.2.6 any longer, you need to upgrade to 3.0.RC2.
This may not fix it, but it will at least produce the latest debug-logs.
Also please try to get a different log. It may or may not work (I had repeated cases were the underlying log engine did not write the data, and yet don't know why)
Run your lazarus IDE as follows
/path/to/lazarus/lazarus.app/Contents/MacOS/lazarus --debug-log=/path/to/yourfiles/laz.log --debug-enable=DBG_CMD_ECHO,DBG_STATE,DBG_DATA_MONITORS,DBGMI_QUEUE_DEBUG,FPDBG_DWARF_ERRORS,FPDBG_DWARF_WARNINGS,FPDBG_DWARF_DATA_WARNINGS,DBG_VERBOSE,DBG_WARNINGS,DBG_STATE,DBG_EVENTS,DBG_THREAD_AND_FRAME,DBG_ERRORS
/path/to/lazarus/lazarus.app/ may be somewhere in your home folder if you installed packages into the IDE. Unfortunately I don't have the exact path (I don't work much on Mac).
If it works it should produce a more detailed log of the lldb interaction.
You may also want to try to uninstall and reinstall xcode, or otherwise force it to re-install itself. Or if you are on the latest xcode, try downgrading to the previous.
Recent
