Does vwatch still work?

[justsomeguy]

I've watch the video. It appears that debug doesn't seem to work for me.

I wrote a simple program to test, set some break points, and try to retrieve the call stack.



The watch list never pops up even though I have selected variables.

The program then remains frozen and will no longer function. I have to kill the process.

I'm sure its something stupid I'm doing.

I'm running Linux and v3.13.0

EDIT:
I went back and checked it on v2.02 and it worked after I changed the port from 9000 to 8080.  I did the same thing with v3.13.0 and it still did not want to work.

[a740g]

I've watch the video. It appears that debug doesn't seem to work for me.

I wrote a simple program to test, set some break points, and try to retrieve the call stack.



The watch list never pops up even though I have selected variables.

The program then remains frozen and will no longer function. I have to kill the process.

I'm sure its something stupid I'm doing.

I'm running Linux and v3.13.0

EDIT:
I went back and checked it on v2.02 and it worked after I changed the port from 9000 to 8080.  I did the same thing with v3.13.0 and it still did not want to work.

Disable Optimization from Compiler Settings, then Debug > Purge C++ Libraries and try again.

[justsomeguy]

I've watch the video. It appears that debug doesn't seem to work for me.

I wrote a simple program to test, set some break points, and try to retrieve the call stack.



The watch list never pops up even though I have selected variables.

The program then remains frozen and will no longer function. I have to kill the process.

I'm sure its something stupid I'm doing.

I'm running Linux and v3.13.0

EDIT:
I went back and checked it on v2.02 and it worked after I changed the port from 9000 to 8080.  I did the same thing with v3.13.0 and it still did not want to work.

Disable Optimization from Compiler Settings, then Debug > Purge C++ Libraries and try again.

Thanks! That was it. I guess I missed that in the video.

[RhoSigma]

Thanks! That was it. I guess I missed that in the video.

No, you didn't missed it. It's simply not in the video, as the Compiler Settings where later implemented in the Phoenix Edition only, that's why it worked out of the box with v2.0.2, it simply doesn't do C++ code optimization and you've no (easy) chance to change that.

However, I've edited the $DEBUG wiki page and added a Problems section to highlight that. BTW - When changing something in the "Compiler Settings" dialog, then you don't necessarily need to do the "Purge C++ Library" step, as the dialog does it already internally on confirmation of the new settings.