Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Build CodeBlocks using Microsoft Visual C++

<< < (6/10) > >>

oBFusCATed:
Why do you think cdb/windbg is better in this?
Why don't you install linux and then use valgrind to see if you're not doing something wrong with the memory?

MortenMacFly:

--- Quote from: oBFusCATed on April 06, 2011, 11:02:22 am ---Why do you think cdb/windbg is better in this?

--- End quote ---
I think what Loaden means is not the debugger, but the debugger integrated in the IDE. So the target is o be able to use the MSVC IDE to debug C::B. This (in fact) might be more comfortable than C::B (although I ma very happy with C::B).

@Loaden: Did you try to connect/debug C::B using gdb from another C::B instance? This way you can debug thread issues for example...

Jenna:
I can not apply the patch on linux. Too many errors (possible a line-ending problem).

MortenMacFly:

--- Quote from: Loaden on April 06, 2011, 10:07:55 am ---Change from:
_("aaa"
   "bbb")
TO:
_("aaa"
_T("bbb"))

--- End quote ---
BTW: This will break translations IMHO, as the second part (now _T("")) will not appear in the translation tables. You should always use _("").

ollydbg:

--- Quote from: MortenMacFly on April 06, 2011, 10:30:03 am ---Also (if you are looking for some work to do ;-)) CC freezes C::B completely if you do a massive search-and-replace in many files across a large (C::B) workspace with multiple projects. This is truly annoying.

--- End quote ---
Oh, catching bugs was quite interesting and challenge for me  :D, but I can't find some annoying bug in CC. (though some parsing errors due to the fact that CC's parser was not a full compiler parser).
Did you use the debugged version of c::b (maybe, run under gdb) to catch some information?

Navigation

[0] Message Index

[#] Next page

[*] Previous page