User forums > Using Code::Blocks

CB 20.03 for windows, debug problems

(1/2) > >>

i386:
I found 2 problems:
1) when using "Debug" functions, a dialog box with title "gdborig.exe has stopped working" prompted sometimes. Then the debug session stopped.
2) In the "Debug mode" with default GCC  and options, I open watch window and find the pointer's address is NOT 64-bit cononical address format, but a normal 32-bit address such as "0x3131b80". But the built out executable is a 64-bti applicaiton according to the file's attribute info.  I think in 64-bit mode, the pointer's address should be "0xFFFFxxxxxxxxxxxx" format.

oBFusCATed:
1. The debugger shipped as part of the 20.03 is not very well working. You should find better one. It is best to use 64bit CB to debug 64bit executables. And the debugger exe should also be 64bit.
2. Most probably this is the output from the debugger. Can you enable full logging and check if the values differ?

i386:
I am using 64-bit win10, and add "-m64" option.
In the code add lines:
    unsigned long long ua = (unsigned long long)pt;
    printf("ua = 0x%016llx\n", ua);
Then compile(no error and warning) and run:
   ua = 0x00000000029924b0
It's just a normal 32-bit address.


--- Quote from: oBFusCATed on April 04, 2021, 10:19:14 am ---1. The debugger shipped as part of the 20.03 is not very well working. You should find better one. It is best to use 64bit CB to debug 64bit executables. And the debugger exe should also be 64bit.
2. Most probably this is the output from the debugger. Can you enable full logging and check if the values differ?

--- End quote ---

i386:
I am sorry! The cannonical address form is OK. Because application runs in ring 3, the upper 16bits is always 0x0000H.

Now left questin 1.

oBFusCATed:
https://forums.codeblocks.org/index.php/topic,24359.msg166152.html#msg166152

Navigation

[0] Message Index

[#] Next page