X-Spam-Check-By: sourceware.org Message-ID: <45EEBDC9.3010009@cygwin.com> Date: Wed, 07 Mar 2007 08:27:37 -0500 From: "Larry Hall (Cygwin)" Reply-To: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.9) Gecko/20061221 Fedora/1.5.0.9-1.fc4.remi Thunderbird/1.5.0.9 Mnenhy/0.7.4.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: managing breakpoints in gdb References: <1d9535c10703070346v3d26bdf2md325e27bd5263e14 AT mail DOT gmail DOT com> In-Reply-To: <1d9535c10703070346v3d26bdf2md325e27bd5263e14@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Domen Vrankar wrote: > I can't set breakpoints in gdb under cygwin with whole path to the > source file: > break "C:/cygwin/home/moon/uart/hello.c:69" > break "/cygdrive/c/cygwin/home/moon/uart/hello.c:69" > > The only thing similar to those two that works is: > break "/home/moon/uart/hello.c:69" > > Can this somehow be set to be able to use the whole path? Is this a > cygwin bug or was cygwin intended to work like that (the version of > gdb is built on linux form the same sources and there the entire path > works OK)? What's not "whole" about /home/moon/uart/hello.c? Perhaps filing a problem report as described by would have made this question moot. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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/