From: Chris Faylor <cgf@cygnus.com>
To: Tim Chick <TChick@virata.com>
Cc: insight@sourceware.cygnus.com
Subject: Re: Insight TCL does not understand cygwin filenames
Date: Fri, 09 Jun 2000 17:56:00 -0000 [thread overview]
Message-ID: <20000609205611.B31688@cygnus.com> (raw)
In-Reply-To: <009f01bfd212$374cd650$eedba8c0@tjc1laptop>
On Fri, Jun 09, 2000 at 01:57:06PM +0100, Tim Chick wrote:
>When I compile a simple hello.c file with cygwin gcc,
>say /src/test/hello.c
>then try to debug this file with insight, I get a stack
>trace, "could not stat file /src/test/hello.c"
This has been recently discussed on the insight and cygwin mailing
lists. I will be uploading a new version of gdb to
ftp://sourceware.cygnus.com/pub/cygwin/gdb
sometime tonight. It should rectify this problem.
However, as I have just pointed out in another message, insight
has never had the ability to open files based on cygwin paths
when using a dialog box.
>The tcl supplied with insight does not understand cygwin
>filenames, so tries to stat "\src\test\hello.c"
>
>As I have / mounted as e:\cygwin1.1, tcl should try to stat
>E:\cygwin1.1\src\test\hello.c
>
>Modifiying the Tcl_TranslateFileName function, in
>insight-5.0\tcl\generic\tclFileName.c as follows
>corrects this, and Insight works correctly.
>
>Compare: (<)E:\cygnus\src\original\insight-5.0\tcl\generic\tclFileName.c
> with: (>)E:\cygnus\src\insight-5.0\tcl\generic\tclFileName.c
>
>923a923,927
>> char dos_name[PATH_MAX];
>>
>> cygwin_conv_to_win32_path( name, dos_name );
>>
>> name=dos_name;
>
>Note that if I happened to have / mounted as E:\ insight
>would have worked without the above patch.
You might want to consider sending a patch and a ChangeLog entry
to gdb@sourceware.cygnus.com to see if it will be accepted into
the mainline sources.
cgf
next prev parent reply other threads:[~2000-06-09 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-09 5:57 Tim Chick
2000-06-09 17:56 ` Chris Faylor [this message]
2000-06-12 10:37 ` Syd Polk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20000609205611.B31688@cygnus.com \
--to=cgf@cygnus.com \
--cc=TChick@virata.com \
--cc=insight@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).