Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <20000526170354.14156.qmail@web109.yahoomail.com>
Date: Fri, 26 May 2000 10:03:54 -0700 (PDT)
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To: earnie_boyd AT yahoo DOT com
Subject: Re: Troubles with gdbtk
To: "Scott A. Hill" <s DOT a DOT hill AT larc DOT nasa DOT gov>,
        cygwin users <cygwin AT sourceware DOT cygnus DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

--- "Scott A. Hill" <s DOT a DOT hill AT larc DOT nasa DOT gov> wrote:
> Earnie,
> 
> I've been having a similar problem ever since I transitioned from V1.1.0 to
> V1.1.1.  When I execute the command
> 
>     > gdb msr
> 
> on an executable that has been compiled and linked with the -g option, the
> gdb gui interface pops up and an error window opens to inform me
> 
>         couldn't stat "/e/Programs/MSR/msr.f": no such file or directory
>            while excuting
>         "File mtime $f"
>         etc
> 
> Once the error message is closed, the executable can be run and stops at the
> first pre-defined breakpoint, the assembly code can be displayed and stepped
> through.  Just can't view the original source.  The source resides in the
> same directory as the executable.  Also, since DOS files on binary mounts
> have been causing problems recently, I also tried removing the CR-LF from
> the source but the problem persists.  Hopefully, that provides some useful
> information.
> 
> 

Thanks for replying Scott.  You've described the same problems I'm having.  If
you use the non-GUI (i.e. the -nw switch), the source code is displayed
properly.  This is a feature of the pathing changes I described concerning \ vs
/.  It has caused a bug in gdbtk when it passes the source file name to the tk
routines to display it.  I haven't found where this happens in gdbtk source
yet, it's difficult to debug a debugger that's broken.

Regards,

=====
---
   Earnie Boyd: <mailto:earnie_boyd AT yahoo DOT com>
            __Cygwin: POSIX on Windows__
Cygwin Newbies: <http://www.freeyellow.com/members5/gw32/index.html>
           __Minimalist GNU for Windows__
  Mingw32 List: <http://www.egroups.com/group/mingw32/>
    Mingw Home: <http://www.mingw.org/>

__________________________________________________
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
http://invites.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com