GDB behaves differently on the final cygwin1.dll 1.7.16 and on a previous one.

[Evgeny Tarasov <teval at yandex dot com>]

Well,

I've got two different cygwin1.dll's of 1.7.16 version.
The first one was obtained from cvs and built by myself (is it attached to 5th june, 2012; as uname -a says)
The other one is of final 20 july, 2012 ver.

So my question is the following:
Why the same GDB does not want to put breakpoints to the same (and any) source when I work with the latest of the two.
I always have completely updated cygwin installation, but in order to debug, i have to replace the latest cygwin1.dll with the previous.

NOTE. However, if my executables and sources reside on the other partition (different from the partition of CYGWIN itself), gdb (with the latest cygwin1.dll) works well.
I.e., gdb establishes a breakpoint by command:
break /cygdrive/d/cygwin/home/user/project/file.cpp:<line>
And (there will not be any exaggeration to say) it refuses to do that by command
break /cygdrive/c/cygwin/home/user/project/file.cpp:<line>
;-)
the version of the 5th june works well in the both cases.

Which kind of info should I provide if so?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple