Debugging MinGW build with VC++ 2005

Andreas Pakulat apaku at gmx.de
Sat Dec 22 17:26:48 CET 2007


On 22.12.07 17:12:15, Christian Ehrlicher wrote:
> Andreas Pakulat schrieb:
> > Hi,
> > 
> > after registering myself with M$ (sigh) and getting the registration key
> > I was able to re-surrect my VC++ 2005 install.
> > 
> > However the instructions from techbase don't seem to work here, that is
> > 
> > a) I don't have a project-specific symbol path setting, only the one
> > under the global options
> > b) that global options-thing seems to expect .pdb files (so the same
> > problem as with windbg)
> > c) VC++ doesn't seem to use export symbols from dll's at all, at least
> > it doesn't find any debugging symbols whatsoever when trying to start
> > kdevelop.
> > 
> > So I'm wondering wether debugging a mingw-built executable in VC++ is
> > going to work at all, and if so what I'm doing wrong? If its not
> > possible I'll change the techbase page accordingly.
> > 
> You can't dbug mingw libs with msvc and vice versa.

Yikes, that basically means no win32 support from my side I fear - at
least not unless someone finds a half-decent working gdb-frontend.
Eclipse doesn't work, KDevelop4 needs Windows porting (and I'm not sure
thats easily doable by me, as it currently seems to use some tty-stuff)
and I can't find any Insight binaries.

Andreas

-- 
You are the only person to ever get this message.



More information about the Kde-windows mailing list