User forums > Using Code::Blocks

Cygwin and Unix Style Paths

<< < (2/2)

reckless:
yep getting same behaviour in some projects on msys its damn annoying.

normally i can get around it by sifting through the makefile usually i hit something like this $(SOMETHING)/$(SOMETHINGELSE) and then removing the / between them.
but thats is at best a hack not a workaround.

nightlight:

--- Quote from: reckless on November 30, 2010, 02:43:15 pm ---yep getting same behaviour in some projects on msys its damn annoying.

normally i can get around it by sifting through the makefile usually i hit something like this $(SOMETHING)/$(SOMETHINGELSE) and then removing the / between them.
but thats is at best a hack not a workaround.

--- End quote ---

Checking the debugger plugin source, I noticed a method GDB_driver::DetectCygwinMount where they check for the presence of Cygwin and obtain the virtual cygdrive prefix from registry. Since cygwin has changed in the latest rev 1.7 its handling of registry (it took everything out), the debugger plugin failed to detect the cygwin and then misbehaved as described above. Looking through older cygwin docs, I found the piece that debugger plugin is missing, put it in the registry by hand and gdb started working correctly.

Here is the fix:

1. Run regedit and locate in registry the key:

   HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2

2. Right click in the right pannel (it's empty since cygwin 1.7) and select New,
    then submenu "String value". It will ask you for the string name - enter:

    cygdrive prefix

    then right click the name to set the string value as:

    /cygdrive


Restart C::B and the debugger will now work.

Navigation

[0] Message Index

[*] Previous page