I do not know, what causes this run error. Especially since normally the are 3 digits (eg. run error 201).
But it is not likely to be the debugger setup.
Couple of checks. If you upgraded from an older Lazarus.
- Environment options > "Files" there is an edit "compiler path". It points to an fpc.exe. Make sure this is indeed 2.6.
- From the debugger settings, find the gdb exe. And run it from command line. It should report version 7.3.50
When you run an app in the debugger, and have the main unit open (unit that has the main form). You should see "blue dots" in the gutter (left side, where line numbers are). You might need to scroll down, they only occur for lines with executable code.
If all that is the case then the setup should be correct.
-----------
If you want to debug code in a package like LazReport, you need to enable debug info in the package and recompile the package.
However that may not be needed here....
-----------
Getting this error could even mean, that the debugger is working.
LazReport may intentionally throw this error and catch it (try except)
Or it may be a bug in LazReport (using a runt error like that is a bit uncommon).
----
If it is intentional:
If you use the app outside the debugger, you will not notice. But the debugger will always inform you about those.
There should be a button "continue", or if the app was paused, you can press F9.
There will likely be a 2nd message about an exception. Same here, use continue.
As for Exceptions you can add them to an ignore list.
----
If it is a bug:
It may still be ignored outside the debugger...
It will require some sample code, so some one who knows LazReport can reproduce it.
-------------
If there are still concerns about the debugger itself. There is some info here:
http://wiki.lazarus.freepascal.org/GDB_Debugger_Tips#Log_info_for_debug_sessionPlease provide the "debug output" as described there.