lvgl / lv_port_win_codeblocks

Windows PC simulator project for LVGL embedded GUI Library
MIT License
129 stars 79 forks source link

codeblocks not escaping 'debugging session' / simulation #1

Closed bishibashiB closed 5 years ago

bishibashiB commented 5 years ago

HI! First of all thanks for providing this nice lib and even adding this handy simulation posibilities~!!

More or less from my start using the codeblocks sim I am experiencing some instabilities from exiting my lvgl GUI simulation. I compile and the start the debug session / simulation. When I am going for the next interation (stop sim, recode, restart sim) the GUI simulation does not end, codeblocks freezes. I have to forcefully kill the codeblocks and additionally end the littleVGL.exe in the processes list. (Codeblocks is telling me something like 'codeblocks is in the middle of compiling ... do you really wanna quit?') Then it will give me a new try. This however is not happening all the time but around 50% of me trying to end my simulation. I tried running codeblocks in admin mode, but no luck. For sure this can be independently from the codeblocks thing or have something to do with the mingw32/64 installation? More about my system producing the problem: it's Win10, what should I add here? Can I provide you some debug system information to get this ruled out? Sorry, but could you assist me in this? (If anything I am more used to debugging embedded stuff rather than Windows apps.)

BR

embeddedt commented 5 years ago

@Jekyll555 Hi,

Did you use the close button on the LittlevGL window or did you try to use the Codeblocks button? I wrote the Windows code and the Codeblocks button doesn't work at the moment.

bishibashiB commented 5 years ago

HI @embeddedt ,

thanks for your quick reply! I tried closing the simulated GUI as well as the 'stop debug session'. Both giving me a ~50% chance of having a successful exit. I got the impression at some time that if I clicked the GUI a few times and then stoped the sim (ether way) I got a sligthly higher chance of successfully exiting.

embeddedt commented 5 years ago

@Jekyll555 I just tested the project now and both buttons work 100% of the time. I tried it at least 20 times.

Have you made any changes to the project at all?

bishibashiB commented 5 years ago

I am trying to confirm the closing behaviour with your comment in mind. Currently: This seems to work:

I wil do a few more tests and get back here. If I skip using the 'X' Gui closure it is fine for me. I yet understand from your last comment that even this 'X' closeure should work... I am working directly from the GIT sandbox updated today (incl. submodules). I would assume no interesting changes (only screen size). I will continue with your input and get back if the picture gets a little clearer.

If it helps your issue tracking you could close the issue here, that's fine for me.

embeddedt commented 5 years ago

@Jekyll555 That is correct. Both the Windows close button and the Codeblocks "end debug" button have identical behavior on my end.

It's fine to leave the issue open since the problem isn't solved yet.

bishibashiB commented 5 years ago

Another rectification: I did not have any crashes for a few tests when sticking to the 'end debug session' button. However it required sometimes more than a single click (2, 3) to exit debug session...

stale[bot] commented 5 years ago

This issue or pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

embeddedt commented 4 years ago

@Jekyll555 https://github.com/littlevgl/lv_drivers/commit/dd32300dce1caeb2f861e03a5a1b150449a6222e should have fixed this problem. You will have to update the lv_drivers submodule within this repository manually, or wait for me to update the whole repository.

bishibashiB commented 4 years ago

Hi @embeddedt So kind to still remember & notify! That'll be a good trigger to restart some activities!

embeddedt commented 4 years ago

I've updated the repository to 6.1, so this problem should be fixed in any new version that you download.