News:

As usual while waiting for the next release - don't forget to check the nightly builds in the forum.

Main Menu

Watch Window not working in Custom Debugger Plugin

Started by tsrinivasanece, June 12, 2019, 12:49:13 PM

Previous topic - Next topic

tsrinivasanece

Hi,
Codeblocks recently changed the debugger plugin for Memory range watches & renamed function name from DbgCmd_UpdateWatchesTree to DbgCmd_UpdateWindow.

We trying to port these watch related changes to our custom debugger plugin we noticed.

After porting the codeblock changes to our custom debugger plugin, we added variable to the watch window & then try to stop & see the variable in the watch window, but "DbgCmd_UpdateWindow" not clearing from the queue. It is halt in the command itself.

Kindly assist us to resolve this issue.

Regards,
Srinivasan

oBFusCATed

Is this plugin copy-pasted from the gdb plugin?
DbgCmd_UpdateWindow is internal to the gdb plugin, you're not supposed to use it in your plugin.
(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!]

tsrinivasanece

Hi,
Thank you for the response.

Yes. But previously we used DbgCmd_UpdateWatchesTree function in our plugin. Watch window was working fine previously.

But now after moved to DbgCmd_UpdateWindow not working.

Regards,
Srinivasan

oBFusCATed

You have to debug it to see what is going on. I cannot help you, because I don't know how your plugin works, nor what modifications you've made to the gdb's plugin source code.
(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!]

tsrinivasanece

Hi,
Thank you for your prompt response.

Can you provide general guidelines for how to debug the codeblocks source code like step in/step out?

Is there way to record log information?

Which will be help us to debug this issue.

Regards,
Srinivasan

oBFusCATed

There is nothing special... Regular debugging - start cb under cb and use the debugger plugin. Set breakpoint, printfs, inspect variables.
(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!]