User forums > Help

debug watches issue

<< < (2/3) > >>

oBFusCATed:
Is it really crashing or it is non-responsive and taking 100% cpu (on a single core)?

olaf888:

It is a 100 % no response crash and I have to restart cb.
look here:
https://www.youtube.com/watch?v=xE4Z9Z8GM80

oBFusCATed:
I guess you don't make a difference between stuck and crashed.

A crash is when the applications encounters some illegal code and the OS stops it. The effect on windows is that you see the 'Don't send dialog'.
If the application is stuck then it is not responsible, but still working and using 100%. So if you wait long enough it might finish as long as it is not in an infinite loop state.

So, do you see a crash or an stuck application?

olaf888:
codeblocks.exe process do 25 % of quad core work
I can move the window but in the windows nothing works.
until os give me that error window:
"Code::Blocks IDE don't responding"
"Close application"
"wait"

For me it seems that the watch process prints out mybuf content until "0" but there is no.
How can I adjust:  print the first 20 bytes of a pointer like the memory dump ?

Zero is the termination character in ascii text . For example
printf("%s",memory);  prints until a zero stops it or an exception is thrown.

oBFusCATed:
Add "set print elements 200" in the initial commands of the debugger.
In the past we've decided to remove the limit, but I guess this has been a wrong decision.
I'll change the default to 200 in the trunk.

Navigation

[0] Message Index

[#] Next page

[*] Previous page