Codeblocks hung alway when debugged windows 32bit program with 64bit cdb. I found the reason that causes this problem by debugging: The command prompt is the form like "0:000:x86>" when debugging 32bit program with 64bit cdb, but the form codeblocks expects is like "0:000>".
Good, but this patch breaks the original case when using 32bit cdb.
Would you be kind enough to provide a patch that works in both cases?
I'm mostly using linux, so cannot test this easily.
Thanks for replying so quick. I have tested the patched version with 64bit cdb on my windows 7 and 32bit cdb on my windows xp in virtual machine. they both work. the original regex match for cdb promt is:
the patched version is:
the patched version matches string "x86" 0 or 1 times, so it work with 64bit, and is compatible with 32bit.
I found another problem with cdb in the original version existed and described in the ticket #430. To make cdb work completely, I hope applying those two patches.
Can you show me some output from both versions, so I can add some tests?
FYI: There is a separate project to create a better CDB debugger plugin. You can try it and see if it works better.
32bit cdb output is as follow:
64bit cdb will encounter two breakpoints after load. The first is as follow:
Input command 'g' to continue. It will encounter the second breakpoint as follow:
This time causes the problem, and so the after do. The same problem has been described before in
http://wiki.codeblocks.org/index.php?title=Debugging_with_Code::Blocks#Use_32bit_CDB_for_32bit_programs_and_64bit_CDB_for_64bit_programs
and http://forums.codeblocks.org/index.php?topic=19372.0.
The compromised solution is using 32bit cdb instead of 64bit. But my 64bit debugger in WDK is used for other development, and I don't want to install 32bit instead of it. so I made the patch after found the reason that caused this problem.
Last edit: Debugfan Chin 2016-11-09
Applied in svn. Thanks for contribution.