From: "Dave Korn" <dave.korn@artimi.com>
To: <cygwin@cygwin.com>
References: <1d9535c10703070346v3d26bdf2md325e27bd5263e14@mail.gmail.com> 	 <45EEBDC9.3010009@cygwin.com> <1d9535c10703070632h4470f151vb889cca938ff1921@mail.gmail.com>
Subject: RE: managing breakpoints in gdb
Date: Wed, 7 Mar 2007 15:08:18 -0000
Message-ID: <01ee01c760ca$71aaaea0$2e08a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <1d9535c10703070632h4470f151vb889cca938ff1921@mail.gmail.com>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 07 March 2007 14:32, Domen Vrankar wrote:

> The problem is that a graphical IDE that serves as gdb frontend and
> works under windows (mo cygwin) sets breakpoints like this:  break
> "C:/cygwin/home/moon/uart/hello.c:69". 

  Ah, that's your problem.  The IDE is a buggy heap of garbage.  You need to
fix it or use a different one.

> If I understand correctly cygwin folder is root and home and cygdrive
> are its subfolders so all I am asking is why cant I access home
> through C:/ ... as cd C: command works and why can't I use /cygdrive/
> ... path to set a breakpoint and can this be enabled/overwritten
> somewhere in some script file or something like that?

  Because the path to the source code is embedded in the executable at compile
time, based on the exact path you passed to the compiler, and if you want gdb
to find it later, the path you supply has to match up.

  In particular, gdb is not aware of mount-points or cygdrive or any other
reason why two seemingly-different paths might in fact refer to the same file.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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