Pelles C forum
Pelles C => Bug reports => Topic started by: leandrojardim on June 12, 2014, 03:50:10 AM
-
Hi, Pelle. :)
I love Pelle's C, its simply amazing the number of enhancements you have put on every new release, like adopting the new C standards, and so on!
I love Pelle's C resource editor too, and its GUI designer, it even reminds me of VisualBasic some time ago. But I dont understand why, sometimes it writes corrupt resource files to disk. It happens very frequently when changing IDs, but seems to be very random, they not happens always. Please check, if you can :)
The editor is wonderful, but there is one issue I have and that is very frequent. The first is that sometimes the editor corrupts the UNDO buffer memory after many uses of the undo and redo keys, and the text appears scrambled. Its random, unfortunately! Please check this one too, if possible. :)
With version 7 when the editor crash I lost changes to my source code many times, both the backup and the original file. But since 8.0 it not had any crash, so I could not reproduce it anymore. Thanks, my hero! :D
The [debugger] is very intuitive, one more point for you :). But since version 7 or earlier I dont remind very well, the toolbar gets totally disabled when I click on any IDE bottom tabs and the only way to enable it again, is to click on any tabs of the text editor. Oh, really annoying. :) If you can, please check this too, thanks. :)
[EDIT: In the last paragraph I changed the word "editor" to "debugger", because it was wrong.]
-
Another thing, seems that the IDE cant put breakpoints on some codes between blocks, like for example, "while" loops and "switch" clauses. This issue is getting stronger at every release. And the code formatter sometimes breaks block separators wrong, seems that it formats the text randomly for each block.
-
Another thing, seems that the IDE cant put breakpoints on some codes between blocks, like for example, "while" loops and "switch" clauses. This issue is getting stronger at every release.
This can be a side effect of optimizations. You have the same problem on code with optimizations off?
-
Yes, I did disable all optimizations, and code inlining, too (only for testing). I did enable debugging with COFF and CodeView.
-
Have you already tried without any optimization and without any debugging?
-
Have you already tried without any optimization and without any debugging?
Stefan he *is in* a debug session.
-
Yes, I set the breakpoints for a debug session, and when I click the debug icon, the breakpoints are deactivated and Pelle's C says the region not has machine code associated.
This is an interesting issue, and happens most when I set breakpoints over source code inside a "case" clause on a "switch" block, for this issue have effect the "case" clause need to have more than one exit, that is "break" statements inside it and on an "if" block, for example.
-
I love Pelle's C resource editor too, and its GUI designer, it even reminds me of VisualBasic some time ago. But I dont understand why, sometimes it writes corrupt resource files to disk. It happens very frequently when changing IDs, but seems to be very random, they not happens always. Please check, if you can :)
Way too much code to go through hunting for a potential bug. It could be your machine too, you know.
You will have to make it reproducible before I can do anything...
The editor is wonderful, but there is one issue I have and that is very frequent. The first is that sometimes the editor corrupts the UNDO buffer memory after many uses of the undo and redo keys, and the text appears scrambled. Its random, unfortunately! Please check this one too, if possible. :)
Same here, really.
The [debugger] is very intuitive, one more point for you :). But since version 7 or earlier I dont remind very well, the toolbar gets totally disabled when I click on any IDE bottom tabs and the only way to enable it again, is to click on any tabs of the text editor. Oh, really annoying. :) If you can, please check this too, thanks. :)
This is by design. The input focus can change, since a number of versions. This solves more problems than it causes.