I started a project and when I first started the project I was able to use the Debug menu to either Run or Debug my project. Somewhere along the way that stopped working and I don't understand why. I am still able to launch the build from the command line but the Debug->Run and Debug->Debug menu items no longer launch the project even though they did at one point.
Klugier Messages: 822 Registered: September 2012 Location: Poland, Kraków
Can you provide more details - about your operating system and upp version you have used? If this is Windows do you use Visual Studio for debugging purpose or you use default toolchain. Do some error message display on the screen while launching debugger? Also, in the help menu there is an option "View application log file" - can you post it when debugger fails to launch.
Few years ago we had a problem that some garbage Visual Studio process was spawn and blocked the execution of debugger. However, these problems were fixed. If nothing helps please restart your computer or at least TheIDE.
So I am running on Ubuntu 20.04. I am using the same GCC toolchain. Like I said when I first used the app my project would start the debugger and execute. Somewhere along the way that stopped happening.
This is all that shows in the application log file:
* /home/steve/IDE/upp/theide 21.11.2020 18:33:05, user: steve
Ok so playing around with it more, setting the working dir in the Run options seems to have fixed the problem. Now if I could only figure out how to get the layout view to go back to widget edit mode when buttons accidentally and mysteriously set it to text mode I would be a happy camper. I have to shut down the IDE in order to get back to where I can actually edit the layouts.
Well now the debugger launches, and if I set a break point it locks up the entire Ubuntu Desktop. The only thing that works while an Ultimate++ app is open in the debugger is the CTRL+TAB function. If I have a terminal open I can CTRL+TAB to the terminal find the process being debugged and kill it on the command line. But what I can't do is step through code that is stopped at a breakpoints because the application or the modal dialog seems to be capturing all events.