Home » Community » U++ community news and announcements » 2020.2rc2
|
|
|
Re: 2020.2rc2 [message #55227 is a reply to message #55226] |
Tue, 20 October 2020 23:01   |
 |
Klugier
Messages: 1099 Registered: September 2012 Location: Poland, Kraków
|
Senior Contributor |
|
|
Hello Mirek,
Will it fix some problems we have with the older version? If yes it is probably worth doing, however the regression may be visible.
What if we made release and at the beginning of the new year we will do next with updated tool-chain? We will have time to test it more properly.
Klugier
U++ - one framework to rule them all.
[Updated on: Tue, 20 October 2020 23:04] Report message to a moderator
|
|
|
|
Re: 2020.2rc2 [message #55229 is a reply to message #55193] |
Tue, 20 October 2020 23:34   |
wimpie
Messages: 46 Registered: March 2013 Location: holland
|
Member |
|
|
mirek wrote on Tue, 20 October 2020 09:40
As there no complaints so far, I am thinking about releasing soon...
I'm mainly running on linux (not this RC per se, I regularly update from github) and I notice a few quircks with debugging (F5) or running (ctrl+F5) but that's probably for another topic.
I tested this release on Windows7, no problems.
Also tested on Windows 10, no problems. I tried packaged Clang and MSVS 2019 community edition
kind regards
edit: removed a few lines I wasn't entirely sure about
[Updated on: Tue, 20 October 2020 23:40] Report message to a moderator
|
|
|
|
Re: 2020.2rc2 [message #55231 is a reply to message #55230] |
Wed, 21 October 2020 00:12  |
wimpie
Messages: 46 Registered: March 2013 Location: holland
|
Member |
|
|
Klugier wrote on Tue, 20 October 2020 23:48Hello Wimpie,
Thanks for reporting! I tested GDB carefully on Linux and it seems that if the breakpoint is place it for very short period of time continue execution and then breaks again. This can be observed only on toolbar - not problem with the debugger behavior. The severity is not majaro - can be fix in the next release. However, for some users it might be noticeable.
Klugier
Hello Klugier,
The debugger itself is not the problem, The bit of weird things are:
- hitting F5 brings up a console, also for GUI programs -- ok.. was this only my problem or has this been fixed last week? it works ok now.
-run (ctrl-F5) with std-out to console truncates the output (when "run with valgrind" output is as expected)
regards,
wimpie
|
|
|
Goto Forum:
Current Time: Sat Apr 26 14:26:38 CEST 2025
Total time taken to generate the page: 0.03115 seconds
|