Author Topic: C::B new releases hung on linkage in cygwin  (Read 10235 times)

Offline littlegene

  • Multiple posting newcomer
  • *
  • Posts: 30
C::B new releases hung on linkage in cygwin
« on: September 07, 2012, 06:53:06 pm »
Hello, dear developers.

I successfully use the latest "debugger branch" (rev 8020) of C::B with my projects and it completely fits my needs for now.
But I recently noted that newest branches (eg, 8300) built locally and curious for me in the future, can not suite me because I saw some particular project of mine does not want to compile well. I realize the cygwin environment often is out of C::B interests, however I would like to report there are problems on project linking stage, not appearing on the mentioned deb_branch of 8020 rev. That it to say - for example, I see the first linkage step of a project does not finish at all at C::B rev 8300. I work with standalone Makefile ("custom Makefile") generated by Autotools in this case, for example, but I think that this fact makes no difference.

Could you offer all possible directions of digging into the trouble from my side. I could give the necessary info of the local trouble if need be.

Thanks.

Gene.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12122
    • Travis build status
Re: C::B new releases hung on linkage in cygwin
« Reply #1 on: September 07, 2012, 08:02:25 pm »
If you have the time and a fast machine you can try to bisect where the problem started.
Probably you can try several nightlies, first.

p.s. If you use custom makefile then there is something broken in the makefile or its expectations (environment variables), because C::B just calls make with your makefile as parameters.
p.s.s. I suppose you've enabled the full compiler log, if not please do so (see the FAQ at the wiki for details)
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline littlegene

  • Multiple posting newcomer
  • *
  • Posts: 30
Re: C::B new releases hung on linkage in cygwin
« Reply #2 on: September 08, 2012, 08:03:29 pm »
If you have the time and a fast machine you can try to bisect where the problem started.
Probably you can try several nightlies, first.

Thank you for your hint. I am in the middle of that proccess right now.
First of all, I would want to beg a pardon for some disinformation concerning my previous message: I had thought I had 8020 working revision of C::B because this branch was being kept by me as standalone set of sources of C::B. But yesterday I realized (after checking many nightly builds) that when compiling that workable version several mounts ago I was at the version *not very close* to 8020 rev. And because I had't have svn.exe utility in the PATH variable (and thus having "SVN 0" rev. in the product banner) I could not say for sure which particular version I was using for the period.

Now, it all is more clear.
For now the affairs is:
- the mentioned trouble of mine with linkage resides in the revisions range from  7800 to 7850.
- Now I keep trying to bisect further and detect the waterline (the two particular adjacent revisions).

will let you know ASAP for the word for further actions.

Offline littlegene

  • Multiple posting newcomer
  • *
  • Posts: 30
Re: C::B new releases hung on linkage in cygwin
« Reply #3 on: September 12, 2012, 07:34:39 pm »
Hello!

I've revealed that problem starts from 7802.
I checked these versions: 7850, 7830, 7815, 7808, 7803(failed to compile), 7802, 7801. (Each time I press Ctrl-F11 for cleanup)
Days ago I tried the newest, as I mentioned, unsuccessfully as well.
7801 - is the latest one where there is no compile(link) trouble. The problem starts (in cygwin) from the next rev. I did not try Linux compilation through C::B for now, though. (In linux I just created new project of this project  from sources and not tried native automake-created makefile.)

svn  Diff and log says there were changes to only compiler plugin.

And  indeed, if I (re)place compiler.dll to 7850, 7830, 7815, 7808 plugins directories, I can successfully compile the project from within these versions ;-)

Any ideas? Should I go on myself or let you check towards this subject?
Here is that line (from build log excerpt):
/bin/sh ../libtool --tag=CXX    --mode=link g++-4   -Wall -g  -fexceptions -all-static -no-undefined   -L/lib/qt3/lib -o libXmlRpc.la -rpath /usr/local/lib strncasecmp.lo XmlRpcClient.lo  XmlRpcDispatch.lo XmlRpcServer.lo XmlRpcServerConnection.lo  XmlRpcServerMethod.lo XmlRpcSocket.lo XmlRpcSource.lo  XmlRpcUtil.lo XmlRpcValue.lo ../replace/libreplace.la


thanks.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12122
    • Travis build status
Re: C::B new releases hung on linkage in cygwin
« Reply #4 on: September 12, 2012, 07:43:45 pm »
What is the difference between the executed commands, if there is a difference?
Also have you tried to put an env command in you makefile to see, if the environment variables are the same with the working and with the broken versions?
Also is the working directory for make the same?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline littlegene

  • Multiple posting newcomer
  • *
  • Posts: 30
Re: C::B new releases hung on linkage in cygwin
« Reply #5 on: September 12, 2012, 08:36:33 pm »
What is the difference between the executed commands, if there is a difference?
Have no idea - what the difference is ;--) All executed commands are the same in ALL cases of compilationa via several C::B.: The custom Makefile is the same always and no matter which additional environment variables I use (in test cases I used none) because I did not even build for these C::B versions the envvars.dll plugin that could control the other ways of build process.

Also have you tried to put an env command in you makefile to see, if the environment variables are the same with the working and with the broken versions?
No, I did not try. I am not aware of how to put "env command in makefile" and for what. 
Makefile was created by a special build target (within C::B) and it was created once.

Also is the working directory for make the same?
Of course. In any C::B I open the same .cbp, choose custom makefile option, and have no envvars that could influence...
I use the same personality profile (*.conf file) in ALL tests.
Other make.exe utilities (in other directories) just unable to compile cygwin sources. CYgwin itself is unique installation per host.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12122
    • Travis build status
Re: C::B new releases hung on linkage in cygwin
« Reply #6 on: September 12, 2012, 09:04:12 pm »
So, if you save the build logs produced by make, they will be the same when using the two versions of C::B (broken and working)?

As you can see in the code, the compiler plugin modifies the PATH variable, it could be that it does it differently in the newer versions.
Can you try to put echo $PATH in some of the rules?

Keep in mind that I don't use cygwin or I've never used it so I have no experience with it.

(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline littlegene

  • Multiple posting newcomer
  • *
  • Posts: 30
Re: C::B new releases hung on linkage in cygwin
« Reply #7 on: September 13, 2012, 09:58:34 am »
So, if you save the build logs produced by make, they will be the same when using the two versions of C::B (broken and working)?
Previously I compared (visually) from the build log only the excerpts where problematic command  (command that hangs) resides, but now ok - I will "file compare" in both cases all previous text lines from the log, till the line where broken compilation hangs.
(But I am still sure - no diff...s)

As you can see in the code, the compiler plugin modifies the PATH variable, it could be that it does it differently in the newer versions.
Can you try to put echo $PATH in some of the rules?
Will try.
Keep in mind that I don't use cygwin or I've never used it so I have no experience with it.
I am aware.



Offline littlegene

  • Multiple posting newcomer
  • *
  • Posts: 30
Re: C::B new releases hung on linkage in cygwin
« Reply #8 on: September 13, 2012, 12:45:19 pm »
As you can see in the code, the compiler plugin modifies the PATH variable, it could be that it does it differently in the newer versions.
Can you try to put echo $PATH in some of the rules?
Yes! I did not guess it myself...
It is what you have described. I put echoing string in a corresponding makefile.am of my proj.
check-local:
   @echo $(PATH)

and the two PATH outputs are different ;-(

The broken build process prints:
/usr/bin:/:/usr/local/bin
While the successful variant prints:
/usr/bin:/cygdrive/c/Program Files/Common Files/NetSarang:/cygdrive/c/Program Files/NVIDIA Corporation/PhysX/Common:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/d/Program Files/Bazaar:/cygdrive/c/Program Files/Microsoft SQL Server/100/DTS/Binn:/usr/local/bin:/cygdrive/c/Program Files/TortoiseSVN/bin:/cygdrive/d/Dev-Cpp/bin

Do you want for me to make a private patch for local usage with newest C::B revisions and cygwin, or you can assume to handle with the situation globally?

Thanks for you help anyway.



Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12122
    • Travis build status
Re: C::B new releases hung on linkage in cygwin
« Reply #9 on: September 13, 2012, 12:50:54 pm »
Do you want for me to make a private patch for local usage with newest C::B revisions and cygwin, or you can assume to handle with the situation globally?
I suppose, we have to wait for MortenMacFly to say something about it, because he has done the change.

Is it possible to provide a test project?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9508
Re: C::B new releases hung on linkage in cygwin
« Reply #10 on: September 13, 2012, 01:54:19 pm »
I suppose, we have to wait for MortenMacFly to say something about it, because he has done the change.
Just noticed this thread.

Is it possible to provide a test project?
This is a requirement to come a step further. The modification was actually needed to really use the compiler as setup and avoid launching a wrong compiler present in the PATH. So this change should not be reverted. However, if it does something different for Cygwin we have to take care. The method used hereby is (however) a wx methods to handle PATH's. So it maybe that we have to do something "by hand" because when it comes to files/path's Cygwin even on Windows is different.

From what I see in the PATH output: Are you really on Windows, or do you cross-compile from Linux? It would be really helpful if you can provide a test project and state your OS and version of Cygwin (DLL).
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline littlegene

  • Multiple posting newcomer
  • *
  • Posts: 30
Re: C::B new releases hung on linkage in cygwin
« Reply #11 on: September 14, 2012, 10:50:24 am »
Now the problem is ultimately clear.

Cygwin hangs on linkage as described (within its own terminal environment, not only within C::B execution) *IF*  PATH set to
"/usr/bin:/:/usr/local/bin". It is a problem of cygwin.
If C::B would modify PATH to more correct
"/usr/bin:/usr/local/bin" instead , then cygwin linkage would function well.

The problem of C::B is in incorrect ("/usr/bin:/:/usr/local/bin" instead of for ex. "/usr/bin:/usr/local/bin") and, may be, unnecessary cutting off the native and very long well PATH that contains many other directories, which do not only belong to linux-like filesystem.

« Last Edit: September 14, 2012, 10:58:40 am by littlegene »

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9508
Re: C::B new releases hung on linkage in cygwin
« Reply #12 on: September 14, 2012, 05:48:25 pm »
The problem of C::B is in incorrect ("/usr/bin:/:/usr/local/bin" instead of for ex. "/usr/bin:/usr/local/bin")
I've just installed a most recent version of Cygwin. Created a console project using the Cygwin compiler - compiling and linking just works for me as it should.

If you don't provide what we asked several times now we cannot help you. Period.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12122
    • Travis build status
Re: C::B new releases hung on linkage in cygwin
« Reply #13 on: September 14, 2012, 06:26:56 pm »
Morten: He is using a custom makefile project and it seems that the env for make is broken.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9508
Re: C::B new releases hung on linkage in cygwin
« Reply #14 on: September 14, 2012, 08:20:36 pm »
Morten: He is using a custom makefile project and it seems that the env for make is broken.
Still: What is so had to provide a minimal test case? I don't see this on our side. In fact I very, very rarely use custom makefiles, so I might even do something wrong. W/O a test case I see no point in "guessing" whats wrong. In the end you can also manipulate the env-vars from the custom makefile. What, if that had happened?
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline littlegene

  • Multiple posting newcomer
  • *
  • Posts: 30
Re: C::B new releases hung on linkage in cygwin
« Reply #15 on: September 14, 2012, 08:59:20 pm »
I suppose, while having
/usr/bin:/cygdrive/c/Program Files/Common Files/NetSarang:/cygdrive/c/Program Files/NVIDIA Corporation/PhysX/Common:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/d/Program Files/Bazaar:/cygdrive/c/Program Files/Microsoft SQL Server/100/DTS/Binn:/usr/local/bin:/cygdrive/c/Program Files/TortoiseSVN/bin:/cygdrive/d/Dev-Cpp/bin

on entry
you should not result in
/usr/bin:/:/usr/local/bin

on exit.

May be this is in SetupEnvironment method (or before)?

Unfortunately I havent look at C::B sources much.

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9508
Re: C::B new releases hung on linkage in cygwin
« Reply #16 on: September 15, 2012, 06:56:32 am »
May be this is in SetupEnvironment method (or before)?
HELLO! ANYBODY OUT THERE??? SAMPLE PROJECT, PLEASE! >:(

How often shall I ask for this again? If you don't provide one next time I am locking this topic. It seems you don't want help, isn't it?
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline stahta01

  • Lives here!
  • ****
  • Posts: 6672
    • My Best Post
Re: C::B new releases hung on linkage in cygwin
« Reply #17 on: September 15, 2012, 06:32:27 pm »
May be this is in SetupEnvironment method (or before)?
HELLO! ANYBODY OUT THERE??? SAMPLE PROJECT, PLEASE! >:(

How often shall I ask for this again? If you don't provide one next time I am locking this topic. It seems you don't want help, isn't it?

Sample Project with Sample Makefile that has the problem you are complaining about.

The exact version of Cygwin DLL and GCC installed in Cygwin is also likely needed.
Make version is really needed because this sounds like an make exe issue to me.

Tim S.
« Last Edit: September 15, 2012, 06:34:48 pm by stahta01 »
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Stretch, compiling CB Trunk against wxWidgets 3.0.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline littlegene

  • Multiple posting newcomer
  • *
  • Posts: 30
Re: C::B new releases hung on linkage in cygwin
« Reply #18 on: September 17, 2012, 08:15:13 am »
Which is the way of providing the test project?
(I have no idea except for forum code tags (that is not sufficient) to provide it)

Attachments ?

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12122
    • Travis build status
Re: C::B new releases hung on linkage in cygwin
« Reply #19 on: September 17, 2012, 08:34:31 am »
Yes, you can zip it and then you can attach it to your post.
Or you can use a pastebin type of service,
or even a filesharing service.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline littlegene

  • Multiple posting newcomer
  • *
  • Posts: 30
Re: C::B new releases hung on linkage in cygwin
« Reply #20 on: September 19, 2012, 01:05:39 pm »
Here is the "test" project

Suppose, it consists of one dummy main.cpp (superfluous) executable and 2 librariers that have to be built as well.
One library named "replace" provided as a sample of good build even in the case Morten McFly modifies the PATH env var in C::B (incl. for "custom" makefile).
The other is an "xml-rpc" lib that is successfully built only inside cygwin console with native, unmodified PATH. "xml-rpc" lib, however, hangs when
building goes via a PATH that is modified in C::B.

You should have in the most recent Cygwin (now 1.7.16):
1. autotools (libtool, automake, autoconf)
2. make utility
3. g++ 4 version of compiler
4. Maybe something else...


Step-by-step after unpacking the test project to a cygwin user directory:

1. Execute cygwin console and go to the project directory
2. sh bootstrap
Now configure script is ready
3. sh runconfigure
Now makefiles all over the directories are ready

4. make all

You should see on entering (or exiting) each particular build directory the current right value of PATH env variable
You should also see that all executables (replace, xml-rpc, and main ) are compiled and built fine.



Step-By-step for building through the custom makefiles (obtained before) in C::B

1. Move testp.conf into the /Users/<user>/AppData/Roaming/codeblocks.
2. With the most recent C::B (eg. rev. 8394) open the testp.cbp project files:
codeblocks /p=ask (choose testp personality)
3. Open testp project (please ignore offers of START PAGE)
4. Correct compiler and linker disk settings already written in, compiler path, ...
I suppose, testp project has custom makefile and compiler full log turned on.
5. Choose MAKEALL build target and Press Ctrl+F11

The project should start rebuilding and during this process you can see current value of PATH env variable at build log as well.
My question is whether the xml-rpc in hung now on your own ? And what do you observe in the PATH value output at build log?

(PATH value now (in 8394 rev) is almost (not fully, as it was in 7801 rev) correct, but the author added (in 7802 rev) '/' directory that breaks the build  :'()



Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9508
Re: C::B new releases hung on linkage in cygwin
« Reply #21 on: September 21, 2012, 07:26:09 pm »
Here is the "test" project
It fails to compile/configure, as all sub-folders are empty. Isn't it possible to reduce it to a minimal hello world example? W/O the need of bootstrap, auto-foo and alike?
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9508
Re: C::B new releases hung on linkage in cygwin
« Reply #22 on: September 21, 2012, 07:29:21 pm »
...btw: I can debug anything compiled with Cygwin just fine (on windows). hence I am using a proper non-makefile based project file and the default debugger. I just set a BP in your (Cygwin based) hello world app and it stopped there just fine.

Maybe you are doing things too complicated?! I mean: You have an IDE here, use its power!
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline littlegene

  • Multiple posting newcomer
  • *
  • Posts: 30
Re: C::B new releases hung on linkage in cygwin
« Reply #23 on: September 21, 2012, 09:45:15 pm »
Thank you for your reply.
The correct test project will be posted  (size < 128k) tomorrow again. If it is not time consuming, please check it then.
I am rather doubt in my mind: None of things you wrote does not work at me:
1. I prefer use autotools and need a outer makefile (and of course in tha same project I also have several native C::B build targets  (specially for debug purpose) which are completely nice )
2. I have to apply (each time) well known patches for gdb in cygwin and force C::B to really work in debugging
3. Now cygwin has a problem that establishing BP in mount-like style (as C::B does: /cygdrive/c/cygwin/home/user/....) succeeds only if debugging project is on the other logical disk that Cygwin deploy folder...
(for item 3: I have (checked) 3 computers with that state : one job computer and 2 notebooks )

How you succeed in these 3 things - enigma for me )

talk to this place later.

thanks, again.


« Last Edit: September 21, 2012, 09:49:21 pm by littlegene »

Offline littlegene

  • Multiple posting newcomer
  • *
  • Posts: 30
Re: C::B new releases hung on linkage in cygwin
« Reply #24 on: September 23, 2012, 06:53:48 am »
Here is the "test" project
It fails to compile/configure, as all sub-folders are empty. Isn't it possible to reduce it to a minimal hello world example? W/O the need of bootstrap, auto-foo and alike?
Unfortunately, autotools withdrawal is quite complicated for me... And Hello world example always compiles fine. Remember: we have to watch the situation then C::B PATH env var substitution *influences* on cygwin compilation bugs in some cases.

Adusted test project is right underneath.

Again, please use
sh bootstrap
sh runconfigure
make all

and after that, check "make all" (for testp.cbp) in C::B...




[attachment deleted by admin]

Offline littlegene

  • Multiple posting newcomer
  • *
  • Posts: 30
Re: C::B new releases hung on linkage in cygwin
« Reply #25 on: September 23, 2012, 07:05:30 am »
...btw: I can debug anything compiled with Cygwin just fine (on windows). hence I am using a proper non-makefile based project file and the default debugger. I just set a BP in your (Cygwin based) hello world app and it stopped there just fine.
I bet... you dont' use WIN 7... On XP C::B is just fine on debug cygwin programs. And it always was capable.
On windows 7 CBplugin (or so) still can't sync  BP with the point in editor and can't open the file in editor.
Without a patch. (I am not presenting here the patch because i use it for me, with no taking into accont all other debuggers can be, besides cygwin, because I NEVER use or used mingw at all)

The main difference (Win XP vs Win 7 on recent cygwin 1.7.16 and recent C::B v.8401) in the both full debugger's logs:

[debug][New Thread 2804.0x850]
[debug][New Thread 2804.0xe8c]
[debug]Breakpoint 1, main () at c:/test1/test1/main.cpp:7
[debug]/cygdrive/c/test1/test1/main.cpp:7:62:beg:0x40117e
[debug]>>>>>>cb_gdb:

At c:/test1/test1/main.cpp:7

against:

[debug][New Thread 2420.0x990]
[debug][New Thread 2420.0xd04]
[debug]Breakpoint 1, main () at C:/test1/main.cpp:7
[debug]/cygdrive/c/test1/main.cpp:7:62:beg:0x40117e
[debug]>>>>>>cb_gdb:

Cannot open file: /cygdrive/c/test1/main.cpp
At /cygdrive/c/test1/main.cpp:7

Offline stahta01

  • Lives here!
  • ****
  • Posts: 6672
    • My Best Post
Re: C::B new releases hung on linkage in cygwin
« Reply #26 on: September 23, 2012, 09:07:08 am »
FYI:

I just tried to debug Cygwin using MinGW GDB.exe (Debugger name and version: GNU gdb (GDB) 7.4) and it worked under Windows 7 32 bit.
Note: I do not normally use the debugger, so the only thing I tested is that it stopped on a break point.
I did see that Cygwin GDB.exe failed to stop on a break point.

CB Self built against wx 2.9 truck; CB SVN 8404.

I am now updating Cygwin to see if that breaks it.



Tim S.
« Last Edit: September 23, 2012, 09:11:53 am by stahta01 »
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Stretch, compiling CB Trunk against wxWidgets 3.0.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline littlegene

  • Multiple posting newcomer
  • *
  • Posts: 30
Re: C::B new releases hung on linkage in cygwin
« Reply #27 on: September 24, 2012, 07:50:48 am »
I did see that Cygwin GDB.exe failed to stop on a break point.
Here is how you can avoid it and force BP be established

1. If your recent cygwin (1.7.16, from 20 july 2012  - check "uname -a") is on the C DISK (C:\CYGWIN), then
place your cygwin project on the other disk, say D: (ex: D:\somedir\someproj\....)

2. If your recent cygwin (1.7.16, from 20 july 2012  - check "uname -a") is on the D DISK (D:\CYGWIN), then
place your cygwin project on the other disk, say C: (ex: C:\somedir\someproj\....)

Then rebuild the program and after that debugging will work.

In other words - a project to debug should lay on the other logical(or phisical) disk than the Cygwin deploy folder...
It is a bug of cygwin, not even discussed so far on cygwin forums, because they IGNORE this notice conserning to this bug...


*BUT* Keep in mind, that after BP in cygwin debug is fired, you could check in C::B (what I wrote about) that:

Cannot open file: /cygdrive/c/test1/main.cpp
At /cygdrive/c/test1/main.cpp:7


As you can see ("At /cygdrive/c/test1/main.cpp:7") BP is workable, but C::B opening of source file break. (Win7 only)