User forums > Using Code::Blocks
GDB (cygwin-special) Warning: /cygdrive/... No such file or directory
DynV:
Yes I did search! But you might not be convinced just yet so here's the google search and unfortunately this site use POST for search so attached is the screen-shot.
I have Code::Blocks 10.05 and CYGWIN_NT-6.0 1.7.9(0.237/5/3) on Windows Vista. I configured my compiler settings exactly as Installing Cygwin Compiler show. and am trying to debug with Cygwin.
Usually before debugging, one would want to compile and I haven't manage to do that
--- Quote ---"PROJECT_NAME - Release" uses an invalid compiler [YOUR ANSWER IS ALREADY THERE. SEARCH THE FORUMS!]. Probably the toolchain path within the compiler options is not setup correctly?! Skipping...
Nothing to be done.
--- End quote ---
but I have managed to go further for debugging
--- Quote ---Building to ensure sources are up-to-date
Build succeeded
Selecting target:
Debug
Adding source dir: C:\Users\REST_OF_PATH\PROJECT_NAME\
Adding source dir: C:\Users\REST_OF_PATH\
Adding file: bin\Debug\PROJECT_NAME.exe
Starting debugger:
done
Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting breakpoints
Debugger name and version: GNU gdb (GDB) 7.3.50.20111026-cvs (cygwin-special)
Warning: /cygdrive/c/Users/REST_OF_PATH/C: No such file or directory.
Warning: /cygdrive/c/Users/REST_OF_PATH/PROJECT_NAME/C: No such file or directory.
--- End quote ---
although not by far. :-\
My main concern has been to debug so far since I want to develop that way and push come to shove I can do the final compilation at my occupation place. The most enlightening topic (of this forum) was Cygwin and Unix Style Paths although it doesn't apply as I already have cygdrive prefix in HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2 (being a Windows registry path) as the attached image show. The most recent topic is Code::Blocks debugger plugin and Cygwin but I don't really know what to do to help me work around this problem. ???
I would be most appreciative if you can help me to debug on C::B using Cygwin.
[attachment deleted by admin]
MortenMacFly:
--- Quote from: DynV on January 26, 2012, 09:23:43 am ---I have Code::Blocks 10.05 and CYGWIN_NT-6.0 1.7.9(0.237/5/3) on Windows Vista.
--- End quote ---
That doesn't mean that you have installed the GCC compiler for Cygwin at all. Notice that the default Cygwin does not install the GCC compiler suite. Are you sure that in the path you setup in the tool chain (or in the "bin" folder below that path) you find the executables you setup? Do the executables have exacly the name you provided (this differs depending on what compiler suite you install under Cygwin). Also notice that the article you are referring to is just a template, surely it has to match exactly your Cygwin installation / configuration.
Because it doesn't seem the case. As C::B complains most likely correctly it cannot find the compiler's executables you setup.
stahta01:
@MortenMacFly:
The autodetect is broken for Cygwin.
You have to change the exec to match the real Cygwin name as in change "gcc.exe" to "gcc-3.exe" or "gcc-4.exe". And, the auto detect does not work for Cygwin 1.7 even with the above change.
That is the reason I submitted my patch.
@DynV: I tried to update the Wiki directions please see if they work for you.
I never used those directions because I never noticed them before.
Tim S.
DynV:
Attached are my current settings which were the same posting the OP... Well this site limit the attachment to 192k :( so they're linked thumbnails. I tried to find where the configurations are saved so I could have posted the XML, or whatever they're made of, instead.
From the previous version MortenMacFly commented on, I entered the files names then clicked on the browsing button of each ending up close the current version then I opened Windows explorer and made sure I pointed to the right paths then copy-pasted its path content into the corresponding fields.
I really thought Cygwin and Unix Style Paths would help me but as the OP stated, it didn't.
I don't know what to do to get the latest Cygwin & Codeblocks working together: CYGWIN_NT-6.0 1.7.9(0.237/5/3) & Code::Blocks 10.05.
MortenMacFly:
--- Quote from: DynV on January 27, 2012, 05:30:01 am ---Attached are my current settings which were the same posting the OP...
--- End quote ---
OK, I tried a nightly and a fresh installed recent Cygwin. The guide still applies, except that I had to modify the toolchain path by hand to point to the Cygwin base folder and that I had to set the executables either as "gcc-3.exe" or "gcc-4.exe" (and g++-3.exe/g++-4.exe respectively).
I ran a compile on a "hello world" project and it worked from scratch.
The only annoyance is that you see for each compiler / linker step the following warning:
cygwin warning:
MS-DOS style path detected: C:/Dokumente und Einstellungen/morten/Desktop/MyCon/main.cpp
Preferred POSIX equivalent is: /cygdrive/c/Dokumente und Einstellungen/morten/Desktop/MyCon/main.cpp
CYGWIN environment variable option "nodosfilewarning" turns off this warning.
Consult the user's guide for more details about POSIX paths:
http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
But doing what is suggested in the warning silents this, too.
So, I don't know what you are doing wrong, but it is working. Can you provide a tiny, simple sample project, probably?
Navigation
[0] Message Index
[#] Next page
Go to full version