Author Topic: Project - compiler changes do not cause debugger to change  (Read 4547 times)

Offline AndrewCot

  • Almost regular
  • **
  • Posts: 153
Re: Project - compiler changes do not cause debugger to change
« Reply #15 on: June 24, 2021, 12:06:42 pm »
oBFusCATed , the patch is not complete in that there are two non core plugins that need the casting int(cbSettingsType:.....). An example of the failure in the build is:
F:\Andrew_Development\codeblocks_sf\src\plugins\contrib\NassiShneiderman\NassiPlugin.cpp:590:23: error: no match for 'operator==' (operand types are 'int' and 'cbSettingsType')
  590 |     if (event.GetInt()==cbSettingsType::Environment)


By the looks of it the other place are, but check to see that I have not missed any:
line 991   -   src/plugins/contrib/ThreadSearch/ThreadSearch.cpp
line 590  -    src/plugins/contrib/NassiShneiderman/NassiPlugin.cpp

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13438
    • Travis build status
Re: Project - compiler changes do not cause debugger to change
« Reply #16 on: June 24, 2021, 02:11:27 pm »
Feedback on your commit comments: Please leave ticket 209 and 611 open as these changes will not fix them from what I have found in the code.
Have you tried the steps in both tickets? Are you still reproducing the problem?


BTW There are more important bugs to fix than 611 and 209 IMHO.
Yes, GTK3 support is quite pressing problem to fix. Then is a system to test the debugger. Then is writing better debugger plugin.
But all these has nothing to do with the topic discussed here.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]