debugger - still problems with "debugged" tab in launch config. dialog
There are still problems in the debugged tab.
Checking modules doesn't "stick".
Unchecked modules sometimes are interpreted.
Apply and revert buttons gray even if there are changes made.
The check/unchecked/gray-status of folder boxes isn't updated properly.
Checking modules doesn't "stick".
Unchecked modules sometimes are interpreted.
Apply and revert buttons gray even if there are changes made.
The check/unchecked/gray-status of folder boxes isn't updated properly.
Leave a comment
on 2012-06-29 05:09 *
By Vlad Dumitrescu
Status changed from Fixed to New
Status changed from Fixed to New
This is still causing 100% CPU usage with large projects!
Shade reported.
Shade reported.
on 2012-06-29 05:10 *
By Vlad Dumitrescu
Category set to Bug
Shade ticket set to 1.0
Category set to Bug
Shade ticket set to 1.0
on 2012-06-29 05:13 *
By Vlad Dumitrescu
Milestone changed from 0.6 to sprint #33
Milestone changed from 0.6 to sprint #33
on 2012-07-27 08:05 *
By Vlad Dumitrescu
Assigned to changed from login to login
Status changed from New to Ongoing
Assigned to changed from login to login
Status changed from New to Ongoing
After discussing this with Shade, we decided to fix it temporarily by disabling the treelist in the dialog. For larger projects, the widget is difficult to use anyway. In the longer term we need to find another way to select modules to be interpreted.
The downside is that in order to be able to use "attach on first call" and "attach on exit", one has to set a dummy breakpoint in the module, so that it is getting interpreted.
The downside is that in order to be able to use "attach on first call" and "attach on exit", one has to set a dummy breakpoint in the module, so that it is getting interpreted.
on 2012-07-27 08:27 *
By Vlad Dumitrescu
Status changed from Ongoing to Test
Status changed from Ongoing to Test
Ticket #313 will implement another way to select interpreted modules