RE: cygpath error: file name too long

On 10 May 2006 18:22, Capaci, Christopher wrote: > Hi, > > I have two machines which, as far as I know, have the same setup. Using > the same PATH string, one fails when trying to convert it with cygpath > and one doesn't. The error is saying that the file name is too long. Can > anyone suggest s

Re: cygpath problem

On Feb 17 00:23, Hans Horn wrote: > Folks, > > according to the cygpath manpage, I should get the following, given a short > DOS name, e.g. c:\Progra~1: > > cygpath -wl C:\Progra~1--> C:\Program Files > cygpath -ml C:\Progra~1--> C:/Program Files > > however, the -m option completely

Re: cygpath fails with snapshot 20051106

On Tue, Nov 08, 2005 at 11:22:04AM -0400, Rodrigo Medina wrote: >Hi, >With cygwin1.ddl-1.5.18: > >$ cygpath -H >/cygdrive/c/Documents and Settings > >With cygwin1-20051106.dll: > >$ cygpath -H >%SystemDrive%/Documents and Settings This should be fixed in the latest snapshot. http://cygwin.com/sna

Re: cygpath feature suggestion

On Mon, Oct 03, 2005 at 04:29:22PM -0400, Joe Smith wrote: >>In this case, the only PTC required is for the documentation. Take a >>look at 'cygpath --help', the option already exists. It is just not in >>the man page. > >I fail to see what he requested. What he wanted was like 'cygpath -pf >-'

Re: cygpath feature suggestion

In this case, the only PTC required is for the documentation. Take a look at 'cygpath --help', the option already exists. It is just not in the man page. I fail to see what he requested. What he wanted was like 'cygpath -pf -' except that instead of using colons to seperate the path list,

Re: cygpath feature suggestion

On Mon, Oct 03, 2005 at 12:34:58PM -0400, Buchbinder, Barry (NIH/NIAID) wrote: >It would be useful if cygpath could work as a filter, taking in lists of >paths on the standard input and put them out one per line on the standard >output. This could be used as a work-around for > for F in >`c

Re: cygpath + csh bug!

On Tue, Jul 26, 2005 at 08:55:13PM -0400, Ordak D. Coward wrote: >The following command combination in csh/tcsh does not work properly: > >$ echo `cygpath -aw .` > >The result is a truncated "C:". Try doing a set echo_style=none prior to using the echo command. tcsh is interpreting '\' as an

Re: cygpath only works if the path presently exists

"Wheeler, Frederick W (Research)" wrote: > My real concern is converting this //nsk1prn02/c304_p to this > \\nsk1prn02\c304_p. This is a valid win2k printer path that I could pass to > /cygdrive/c/WINNT/system32/print using the /D: option, but cygpath won't > convert it. I don't know if this

Re: cygpath --help -> crash

On Sun, 6 Mar 2005, Arend-Jan Westhoff wrote: > When running: > cygpath --help > apparently a crash occurs. Output: > Usage: cygpath (-d|-m|-u|-w|-t TYPE) [-f FILE] [OPTION]... NAME... > 68 [main] cygpath 1964 handle_exceptions: Exception: > STATUS_ACCESS_VIOLATION > 25808 [mai

Re: cygpath --help -> crash

>When running: > cygpath --help >apparently a crash occurs. Output: > Usage: cygpath (-d|-m|-u|-w|-t TYPE) [-f FILE] [OPTION]... NAME... > 68 [main] cygpath 1964 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION > 25808 [main] cygpath 1964 open_stackdumpfile: Dumping stack trac

Re: cygpath -m (and -w) sometimes emits multi-line names

On Wed, 23 Feb 2005 15:26:18 -, Dave Korn wrote: > Original Message > From: cygwin-owner On Behalf Of Joshua Daniel Franklin > Sent: 23 February 2005 14:25 > > >> 2) What's with the CDATA section ? > > > > A CDATA section is for enclosing text that might otherwise be interpreted > >

RE: cygpath -m (and -w) sometimes emits multi-line names

Original Message From: cygwin-owner On Behalf Of Joshua Daniel Franklin Sent: 23 February 2005 14:25 >> 2) What's with the CDATA section ? > > A CDATA section is for enclosing text that might otherwise be interpreted Yeh, I knew that! I meant "How come it appears in the man page?"

Re: cygpath -m (and -w) sometimes emits multi-line names

On Tue, 22 Feb 2005 15:42:45 -, Dave Korn wrote: > Original Message > >From: cygwin-owner On Behalf Of Raul Miller > > Both the man page and the usage information on cygpath indicate > > that it only accepts a single file name argument. These should > > probably be updated. > > A fa

RE: cygpath -m (and -w) sometimes emits multi-line names

Original Message >From: cygwin-owner On Behalf Of Raul Miller >Sent: 21 February 2005 23:58 > On Sun, Feb 20, 2005 at 03:21:35PM -0500, I wrote: >> My mistake. Sorry. > > On second thought: > > Both the man page and the usage information on cygpath indicate > that it only accepts a si

Re: cygpath -m (and -w) sometimes emits multi-line names

On Sun, Feb 20, 2005 at 03:21:35PM -0500, I wrote: > My mistake. Sorry. On second thought: Both the man page and the usage information on cygpath indicate that it only accepts a single file name argument. These should probably be updated. Expecting behavior similar to windows' cd is plausible

Re: cygpath -m (and -w) sometimes emits multi-line names

On Sun, Feb 20, 2005 at 02:52:47PM -0500, Larry Hall wrote: > cygpath -m "`pwd`/bookmarks.htm" | sed 's} }%20}g; s}^}file:///}' Doh. My mistake. Sorry. Too bad I can't retract my post. Thanks, -- Raul -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports:

RE: cygpath -m (and -w) sometimes emits multi-line names

> -Original Message- > From: cygwin-owner On Behalf Of Dave Korn > Sent: 20 February 2005 20:02 > ? OK, then, so what kind of output would you expect from the command D'oh. Modulo line-wrapping by my mailer, of course, though at least it serves to nicely highlight the presence of spac

RE: cygpath -m (and -w) sometimes emits multi-line names

> -Original Message- > From: cygwin-owner On Behalf Of Raul Miller > Sent: 20 February 2005 19:17 > Manipluating the result of cygpath -m with shell tools is needlessly > difficult. > > $ pwd > /cygdrive/c/Program Files/Mozilla Firefox/defaults/profile > $ cygpath -m `pwd`/bookmarks.htm |

Re: cygpath -m (and -w) sometimes emits multi-line names

At 02:17 PM 2/20/2005, you wrote: >Manipluating the result of cygpath -m with shell tools is needlessly >difficult. > >$ pwd >/cygdrive/c/Program Files/Mozilla Firefox/defaults/profile >$ cygpath -m `pwd`/bookmarks.htm | sed 's} }%20}g; s}^}file:///}' >file:///c:/Program >file:///Files/Mozilla >fil

RE: "cygpath -w ." returns ".\" instead of "."

> From: Igor Pechtchanski > Sent: Friday, July 02, 2004 9:32 PM > Ugh, top posting... Oh, well... Hmm... yes, I always re-edit, for NOT top posting - unless I'm lazy. > FYI, as a workaround, "cygpath -w ./", "cygpath -m ./", and "cygpath -u > ./" should work consistently. Additionally; The -a

RE: "cygpath -w ." returns ".\" instead of "."

Ugh, top posting... Oh, well... FYI, as a workaround, "cygpath -w ./", "cygpath -m ./", and "cygpath -u ./" should work consistently. If you feel that the current behavior is a bug, feel free to submit a patch to the code that does the transformation (in winsup/cygwin/path.cc, the definition of

RE: "cygpath -w ." returns ".\" instead of "."

Okay point taken. Stupid trivial script aside... Why does: "cygpath -w ." return ".\" instead of "." "cygpath -m ." return "./" instead of "." And why does: "cygpath -w dir" return "dir" instead of "dir\" "cygpath -m dir" return "dir" instead of "dir/" Shouldn't: "cygpath -w ." "cygpath -m ." "c

RE: "cygpath -w ." returns ".\" instead of "."

> -Original Message- > From: cygwin-owner On Behalf Of Trevor Baker > Sent: 01 July 2004 22:43 > the following > trivial script: Even a trivial script can have bugs in it! > #-- > #!/bin/sh > > BASEDIR=`cygpath -w .` So here on line one, you're asking for a windoze-format p

Re: Cygpath: Path name conversion Issue

On Jun 8 10:14, Dave Korn wrote: > > -Original Message- > > From: cygwin-owner On Behalf Of john george > > Sent: 08 June 2004 05:23 > > > Hi, > > I'm trying to convert the following path name to a > > unix specific format so that it could be passed as a > > parameter to the Unix "open(..

RE: Cygpath: Path name conversion Issue

> -Original Message- > From: cygwin-owner On Behalf Of john george > Sent: 08 June 2004 05:23 > Hi, > I'm trying to convert the following path name to a > unix specific format so that it could be passed as a > parameter to the Unix "open(..)" system call. > cygpath > "\\Device\\harddiskdmv

Re: cygpath

On Wed, 12 May 2004, Joshua Daniel Franklin wrote: > --- Dave Yost wrote: > [snip] > > I have a small problem. > > > > I have a path ../foo:../bar > > > > When I use the --path argument, cygpath insists on converting the relative > > paths into absolute paths. I wish it wouldn't do that. But I c

Re: cygpath

On Wed, May 12, 2004 at 09:21:36AM -0700, Joshua Daniel Franklin wrote: >>It would be cool if cygpath had an option to resolve any symlinks and >>shortcuts in the path. > >Yes, it would. Patches thankfully accepted. :) I don't see this as a function of cygpath. cygpath is for performing operati

RE: cygpath

> -Original Message- > From: cygwin-owner On Behalf Of Joshua Daniel Franklin > Sent: 12 May 2004 17:22 > > It would be cool if cygpath had an option to resolve any > symlinks and > > shortcuts in the path. > > Yes, it would. Patches thankfully accepted. :) Don't you mean "Patches gra

Re: cygpath

--- Dave Yost wrote: > Thanks for cygpath and whaterver you do for cygwin! Dave, While I have submitted a couple patches to cygpath, a lot of people have put work into it and I certainly can't take credit for the whole thing! Several of these people and other knowledgable cygwin users are on the

RE: cygpath solution

> From: Buchbinder, Barry (NIH/NIAID) > From: Vivek HS > Hi all, > > I had faced the below problem when using the cygpath.exe. > > Below is the data: > Was using cygwin 1.5.8 and the cygpath in that was crashing: > > > 10 [main] ? 1400 cygheap_fixup_in_child: Couldn't reserve space for >

RE: cygpath solution

upgrade to Cygwin 1.5.9-1 -Original Message- From: Vivek HS [mailto:[EMAIL PROTECTED] Sent: Monday, March 22, 2004 1:02 AM To: [EMAIL PROTECTED] Subject: cygpath solution Hi all, I had faced the below problem when using the cygpath.exe. Below is the data: Was using cygwin 1.5.8 and the

RE: cygpath: cygwin heap error with 1.5.8-1

>$ cygpath > 6 [main] ? 1444 cygheap_fixup_in_child: Couldn't reserve space for >cygwin's heap (0x616E <0x46>) in child, Win32 error 487 >C:\Programme\cygwin\bin\cygpath.exe (1444): *** m.AllocationBase 0x0, >m.BaseAddress 0x616E, m.RegionSize 0x1AA, m.State 0x1 > >Searchin

RE: cygpath: cygwin heap error with 1.5.8-1

Actually, http://sources.redhat.com/ml/cygwin/2004-03/msg00811.html reports exactly that problem with cygpath. The solution is given here http://sources.redhat.com/ml/cygwin/2004-03/msg00847.html. (Thanks again to CGF, who fixed this quickly with only a guess of what the problem was.) There have

Re: cygpath: cygwin heap error with 1.5.8-1

[EMAIL PROTECTED] wrote: > 6 [main] ? 1444 cygheap_fixup_in_child: Couldn't reserve space for > cygwin's heap (0x616E <0x46>) in child, Win32 error 487 > C:\Programme\cygwin\bin\cygpath.exe (1444): *** m.AllocationBase 0x0, > m.BaseAddress 0x616E, m.RegionSize 0x1AA, m.State

Re: cygpath --ignore problem

On Mon, 15 Mar 2004, Christopher Faylor wrote: > On Mon, Mar 15, 2004 at 02:58:03PM -0500, Igor Pechtchanski wrote: > >When cygpath is invoked with a --ignore (-i) option, it still prints "Try > >`cygpath --help' for more information." on missing input. Can I still > >send in trivial (essentially

Re: cygpath --ignore problem

On Mon, Mar 15, 2004 at 02:58:03PM -0500, Igor Pechtchanski wrote: >When cygpath is invoked with a --ignore (-i) option, it still prints "Try >`cygpath --help' for more information." on missing input. Can I still >send in trivial (essentially one line) patches without a copyright >assignment? If

Re: cygpath bug (windows 2000)

On Sat, 28 Feb 2004, Christian Matuszewski wrote: > On Fri, Feb 27, 2004 at 11:22:38AM -, Hughes, Bill wrote: > >> Sent: 27 February 2004 10:43 From: Christian Matuszewski > >>cgf says: > >>>Try the latest snapshot . > >> > >>Thank you very much, now cygpath doesn

Re: cygpath bug (windows 2000)

On Fri, Feb 27, 2004 at 11:22:38AM -, Hughes, Bill wrote: >> Sent: 27 February 2004 10:43 From: Christian Matuszewski >>cgf says: >>>Try the latest snapshot . >> >>Thank you very much, now cygpath doesn't crash anymore. >> >>But is it necessary, that cygpath gives

Re: cygpath bug (windows 2000)

On Fri, Feb 27, 2004 at 11:22:38AM -, Hughes, Bill wrote: >> Sent: 27 February 2004 10:43 From: Christian Matuszewski >>cgf says: >>>Try the latest snapshot . >> >>Thank you very much, now cygpath doesn't crash anymore. >> >>But is it necessary, that cygpath gives

RE: cygpath bug (windows 2000)

> Sent: 27 February 2004 10:43 From: Christian Matuszewski ..snip.. > > > > Try the latest snapshot . > > > > > > Thank you very much, now cygpath doesn't crash anymore. > > But is it necessary, that cygpath gives the error message: > cygpath: error converting "/

Re: cygpath bug (windows 2000)

> At 08:02 AM 2/20/2004, Christian Matuszewski you wrote: > >Hello, > > > >the following command crashes: > > > >cygpath -p -m > >/

Re: cygpath bug (windows 2000)

On Fri, Feb 20, 2004 at 02:02:49PM +0100, Christian Matuszewski wrote: >the following command crashes: > >cygpath -p -m >/d

Re: cygpath bug (windows 2000)

At 08:02 AM 2/20/2004, Christian Matuszewski you wrote: >Hello, > >the following command crashes: > >cygpath -p -m >/dd

RE: Re: cygpath hangings: A fix - bash patch enclosed -- bash mai ntainer please note!

>> I am using the latest version of Cygwin (1.5.5-1) on a Windows XP box on a >> domain (tried several fixes pertaining to changing the rights of >> the cygwin >> dir and whole c drive - Everybody full control). >> >> The problem is no command substitution works (using `'s or $()'s). >> >> After a

RE: cygpath hangings: A fix - bash patch enclosed -- bash maintainer please note!

> From: Geoffrey Ruscoe > Sent: Monday, November 10, 2003 8:05 PM > I am using the latest version of Cygwin (1.5.5-1) on a Windows XP box on a > domain (tried several fixes pertaining to changing the rights of > the cygwin > dir and whole c drive - Everybody full control). > > The problem is no co

Re: cygpath hangings: A fix - bash patch enclosed -- bash maintai ner please note!

I'm not sure if this is the same problem, but after searching and searching this was the closest problem I've found (also other references to the setup post-install scripts problem). I am using the latest version of Cygwin (1.5.5-1) on a Windows XP box on a domain (tried several fixes pertaining t

Re: cygpath Suggestion

On Fri, Nov 07, 2003 at 12:06:24PM -0800, Barry Buchbinder wrote: >It might be useful to have a cygpath option that >outputs %COMSPEC% and exits directly and without >needing to do > `cygpath "$COMSPEC"` > >(I know -- PTC -- but I'm not a programer.) This isn't a PTC. It is so trivially easy to

Re: cygpath hangings: A fix - bash patch enclosed -- bash maintainer please note!

On Tue, Oct 21, 2003 at 09:35:38AM -0500, Jason Dufair wrote: >Thanks a lot for this, Christopher. I sit in awe of the efforts of >everyone to fix this extremely tricky bug. As with most bugs, it turned out to be extremely simple to fix once all of the parameters were known. I appreciate all of

Re: cygpath hangings: A fix - bash patch enclosed -- bash maintainer please note!

Thanks a lot for this, Christopher. I sit in awe of the efforts of everyone to fix this extremely tricky bug. Christopher Faylor <[EMAIL PROTECTED]> writes: > On Wed, Oct 15, 2003 at 04:30:12PM -0400, Christopher Faylor wrote: >>I just managed to duplicate the problem on my system at work. >> >>

Re: cygpath hangings: A fix - bash patch enclosed -- bash maintainer please note!

I've just checked the patch a wee bit closer - it looks OK to me. If you want to push it upstream, please go ahead :) I'm wrapping up release -16 now. I'll make it available for upload on -apps ASAP. Thanks, rlc On Sat, Oct 18, 2003 at 01:58:36AM -0400, Christopher Faylor wrote: > On Wed, Oct

Re: cygpath hangings: A fix - bash patch enclosed -- bash maintainer please note!

I'll apply your patch and release a new Bash version shortly rlc On Sat, Oct 18, 2003 at 01:58:36AM -0400, Christopher Faylor wrote: > On Wed, Oct 15, 2003 at 04:30:12PM -0400, Christopher Faylor wrote: > >I just managed to duplicate the problem on my system at work. > > > >Stay tuned. > > I ma

RE: cygpath hangings: A fix - bash patch enclosed -- bash maintai ner please note!

> -Original Message- > From: Hannu E K Nevalainen > Sent: 18 October 2003 13:22 > Subject: RE: cygpath hangings: A fix - bash patch enclosed -- bash > maintainer please note! > > The simple test works flawlessly. > ditto > I've run my setup-b

Re: cygpath hangings: A fix - bash patch enclosed -- bash maintainer please note!

> if anyone wants to try this. It would be good to confirm or deny > that this fixes the problem for everyone. I tried the posted simple shell script with the old and new bash.exe. Worked exactly as you predicted... Hung with the old, didn't hang (i.e. worked) with the new. cygcheck output atta

RE: cygpath hangings: A fix - bash patch enclosed -- bash maintainer please note!

> From: Christopher Faylor > Sent: Saturday, October 18, 2003 8:06 AM > I've put a patched version of bash up at: > > ftp://sourceware.org/pub/cygwin/tmp/bash.exe > > if anyone wants to try this. It would be good to confirm or deny > that this fixes the problem for everyone. > > Btw, maybe this h

RE: cygpath hangings: A fix - bash patch enclosed -- bash maintainer please note!

Christopher Faylor writes: > > > I've put a patched version of bash up at: > > ftp://sourceware.org/pub/cygwin/tmp/bash.exe > > if anyone wants to try this. It would be good to confirm or deny > that this fixes the problem for everyone. > > Btw, maybe this has already been mentioned, but here

Re: cygpath hangings: A fix - bash patch enclosed -- bash maintainer please note!

On Sat, Oct 18, 2003 at 01:58:36AM -0400, Christopher Faylor wrote: >On Wed, Oct 15, 2003 at 04:30:12PM -0400, Christopher Faylor wrote: >>I just managed to duplicate the problem on my system at work. >> >>Stay tuned. > >I managed to duplicate it at home by booting into W2K, too. That meant >I did

Re: cygpath hangings: A fix - bash patch enclosed -- bash maintainer please note!

On Wed, Oct 15, 2003 at 04:30:12PM -0400, Christopher Faylor wrote: >I just managed to duplicate the problem on my system at work. > >Stay tuned. I managed to duplicate it at home by booting into W2K, too. That meant I didn't have to feel guilty about working on this at work. :-) This should fi

Re: cygpath hangings

I must be going senile. I just managed to duplicate the problem on my system at work. I could have sworn that I tried this several times to no avail. Stay tuned. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Docume

Re: cygpath hangings

On Wed, 15 Oct 2003, Christopher Faylor wrote: > I'd be more interested in "cygcheck cygpath" output in the two > different cases. That would tell us which DLLs were being loaded. > No difference. For the stripped down MINGW version of cygpath: Found: .\cyghan.exe cyghan.exe D:\WINNT\System32

Re: cygpath hangings

On Wed, Oct 15, 2003 at 09:19:14AM +0100, Steve Fairbairn wrote: > >All, > >As a side note, I have 11 copies of that DLL (java dev and runtime, Visual >Studio/Source Safe, ...) on my system, but only the system32 one is in my >normal path. > >Someone mentioned something about possible issues to do

Re: cygpath hangings

On Wed, 15 Oct 2003, Igor Pechtchanski wrote: > On Tue, 14 Oct 2003, Brian Ford wrote: > > On Tue, 14 Oct 2003, Igor Pechtchanski wrote: > > >Brian Ford wrote: > > > > There will be no ouput unless main calls foo, right? > > > > > > Actually, if the DLL was loaded, there should be output even if f

Re: cygpath hangings

On Tue, 14 Oct 2003, Brian Ford wrote: > On Tue, 14 Oct 2003, Igor Pechtchanski wrote: > >Brian Ford wrote: > > > There will be no ouput unless main calls foo, right? > > > > Actually, if the DLL was loaded, there should be output even if foo isn't > > called... > > > Just linking to it causes a l

RE: cygpath hangings

> -Original Message- > From: Steve Fairbairn > Sent: 15 October 2003 09:19 > Subject: RE: cygpath hangings > > I ran this first with my normal bash shell, renamed the > output, and then ran > it again from within setup. > > I am attaching the 2 files as t

RE: cygpath hangings

All, As a side note, I have 11 copies of that DLL (java dev and runtime, Visual Studio/Source Safe, ...) on my system, but only the system32 one is in my normal path. Someone mentioned something about possible issues to do with the path being different, so I thought I'd run a quick test. --- $

Re: cygpath hangings

On Tue, 14 Oct 2003, Brian Ford wrote: > On Tue, 14 Oct 2003, chris wrote: > > > If I comment out the call to SHGetPathFromIDList in this program, the > > program returns, else it hangs. > > > Confirmed. > > > Also, This program seems to be both valid c++ and c code. If it is > > compiled in gcc,

Re: cygpath hangings

Chris, On Tue, 14 Oct 2003, chris wrote: > If I comment out the call to SHGetPathFromIDList in this program, the > program returns, else it hangs. > Confirmed. > Also, This program seems to be both valid c++ and c code. If it is > compiled in gcc, all is fine. In g++, it hangs. > Really? I see

Re: cygpath hangings

On Tue, 14 Oct 2003, Igor Pechtchanski wrote: > Does "cygcheck yourprog.exe" show both test_dll.dll and SHLWAPI.DLL? > [EMAIL PROTECTED] ~ $ cygcheck cyghan.exe Found: .\cyghan.exe cyghan.exe G:\cygwin\bin\cygwin1.dll D:\WINNT\System32\KERNEL32.dll D:\WINNT\System32\ntdll.dll .\cygl.d

Re: cygpath hangings

On Tue, 14 Oct 2003, Brian Ford wrote: > Igor, > > On Tue, 14 Oct 2003, Igor Pechtchanski wrote: > > > On Tue, 14 Oct 2003, chris wrote: > > > > > -- Code begins -- > > > > > > #include > > > > > > void fee (void) { > > > char *buf; > > > LPITEMIDLIST id; > > > SHGetPathFromIDList (id, buf)

Re: cygpath hangings

Igor, On Tue, 14 Oct 2003, Igor Pechtchanski wrote: > On Tue, 14 Oct 2003, chris wrote: > > > -- Code begins -- > > > > #include > > > > void fee (void) { > > char *buf; > > LPITEMIDLIST id; > > SHGetPathFromIDList (id, buf); > > } > > > > int main (int argc, char **argv) > > { > > ret

RE: cygpath hangings

> From: Igor Pechtchanski > Sent: Tuesday, October 14, 2003 3:38 PM > FWIW, I've posted instructions on how to run a program from setup recently > (but can't find the actual message at the moment). To summarize, simply > create a shell script named BLAH.sh that calls that program (you may need >

Re: cygpath hangings

On Tue, 14 Oct 2003, chris wrote: > Chris, > > >I suspect that this hang might be happening while loading the DLL. Could > >you try to link your program with something like below and see if it still > >hangs, and what it outputs? If it doesn't hang, try renaming > >SHGetPathFromIDList below to s

Re: cygpath hangings

Steve Fairbairn wrote: -Original Message- From: Cliff Hones Sent: 14 October 2003 15:03 Subject: Re: cygpath hangings Running cygcheck -vs (and/or some other such utility) from a hanging and non-hanging postinstall shell might come up with something. As in set up a script in /etc

Re: cygpath hangings

Chris, I suspect that this hang might be happening while loading the DLL. Could you try to link your program with something like below and see if it still hangs, and what it outputs? If it doesn't hang, try renaming SHGetPathFromIDList below to something else (e.g., foo) that calls the real SHGe

Re: cygpath hangings

Steve Fairbairn wrote: > As in set up a script in /etc/postinstall that runs cygcheck -vs to a file, > and send that in? I would suggest setting up the script to send to a file, invoking it twice by running setup from explorer and from a command line, and if there is any difference send that in.

RE: cygpath hangings

> -Original Message- > From: Cliff Hones > Sent: 14 October 2003 15:03 > Subject: Re: cygpath hangings > > Running > cygcheck -vs (and/or some other such utility) from > a hanging and non-hanging postinstall shell might come > up with something. >

Re: cygpath hangings

I'm surprised that this problem seems so intractable. While careful debugging and analysis ought to get to the root of the problem eventually, there is clearly some difficulty in getting a suitable debug session without upsetting what is being examined. [Heisenberg at work.] So alternate approach

RE: cygpath hangings

On Tue, 14 Oct 2003, Steve Fairbairn wrote: > [snip] > I have suffered from the hanging cygpath issue, I did a clean install (new > box) and have since not changed the installation. If you could supply me > with an exe for this code (private email) or the flags used when building > that code and

Re: cygpath hangings

On Tue, 14 Oct 2003, chris wrote: > I decided to try to put some investigation into the cygpath crashings > that have been reported so much. Here are my findings.. I hope this > helps! I'd be happy to try further debuggings, except I couldn't figure > out how to attach a debugger to the program (b

RE: cygpath hangings

> From: chris > Sent: 14 October 2003 13:33 > Subject: Re: cygpath hangings > > Corinna Vinschen wrote: > > > > >Nope, not for me. Are you, by any chance, still using gcc2? > > > > > Nope, using gcc 3.3.1 (cygming special) > > Just ch

Re: cygpath hangings

On Tue, Oct 14, 2003 at 01:33:03PM +0100, chris wrote: > Corinna Vinschen wrote: > >Nope, not for me. Are you, by any chance, still using gcc2? > > > Nope, using gcc 3.3.1 (cygming special) > > Just checking... have you been suffering from the "cygpath" crashing > during setup? If not I imagine

Re: cygpath hangings

Corinna Vinschen wrote: On Tue, Oct 14, 2003 at 12:44:57PM +0100, chris wrote: Also, This program seems to be both valid c++ and c code. If it is compiled in gcc, all is fine. In g++, it hangs. [...] If there is anything else anyone would like me to try (like taking a -E and picking out all t

Re: cygpath hangings

On Tue, Oct 14, 2003 at 12:44:57PM +0100, chris wrote: > Also, This program seems to be both valid c++ and c code. If it is > compiled in gcc, all is fine. In g++, it hangs. > [...] > If there is anything else anyone would like me to try (like taking a -E > and picking out all the useless bits of

Re: cygpath hang - using gdb

On Thu, Oct 09, 2003 at 08:07:14PM +0200, Hannu E K Nevalainen wrote: >I'll leave this for a day or two now. Good evening. Don't bother. Brian Ford is providing more than adequate feedback. There's no need to strain your temper or subject the mailing list to your frustration with building the too

RE: cygpath hang - using gdb

> From: Christopher Faylor > Sent: Wednesday, October 08, 2003 9:02 PM Hannu: > >Now; Any ideas how to work further on this? > Build a cygwin1.dll with --enable-debugging, install it, build > cygpath.exe, > install it. "set CYGWIN_DEBUG=cygpath" at the command prompt > before running > setup.exe

RE: cygpath hang - using gdb

> From: Christopher Faylor > Sent: Wednesday, October 08, 2003 9:02 PM > No, you've stepped into the part that is hanging, so gdb is > >> waiting patiently > >> for it to return. > >> > >> cgf > > > >Ok. Got that. > >Now; Any ideas how to work further on this? > >Set breakpoints at "random" places

Re: cygpath hang - using gdb

On Wed, Oct 08, 2003 at 08:53:45PM +0200, Hannu E K Nevalainen wrote: > >> -Original Message- >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf >> Of Christopher Faylor >> Sent: Wednesday, October 08, 2003 8:37 PM >> To: [EMAIL PROTECTED] >>

RE: cygpath hang - using gdb

> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf > Of Christopher Faylor > Sent: Wednesday, October 08, 2003 8:37 PM > To: [EMAIL PROTECTED] > Subject: Re: cygpath hang - using gdb > > > On Wed, Oct 08, 2003 at 08:00:21PM +0200,

Re: cygpath hang - using gdb

On Wed, Oct 08, 2003 at 08:00:21PM +0200, Hannu E K Nevalainen wrote: >> I will be investigating the problem in every way that anyone can >> think of as time permits. No promises though, as usual. >> I'll have to learn bits and pieces of cvs and gdb for starters - >> I'll do my best. > >$ MODE=iron

RE: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise

> From: Christopher Faylor > Sent: Monday, October 06, 2003 10:09 PM > To: [EMAIL PROTECTED] > Subject: Re: cygpath hangs from postinstall scripts when called like > $(cygpath -S) but not otherwise > > > On Mon, Oct 06, 2003 at 08:55:12PM +0200, Hannu E K Nevalainen wrot

Re: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise

On Mon, Oct 06, 2003 at 08:55:12PM +0200, Hannu E K Nevalainen wrote: >> From: Igor Pechtchanski >> Sent: Monday, October 06, 2003 4:40 PM > >> On Mon, 6 Oct 2003, Hannu E K Nevalainen wrote: >> >> > > From: Igor Pechtchanski >> > > Sent: Monday, October 06, 2003 1:44 AM >> > >> > > It would be eas

RE: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise

> From: Igor Pechtchanski > Sent: Monday, October 06, 2003 4:40 PM > On Mon, 6 Oct 2003, Hannu E K Nevalainen wrote: > > > > From: Igor Pechtchanski > > > Sent: Monday, October 06, 2003 1:44 AM > > > > > It would be easy to check if the above was the reason for the hang by > > > trying to call the

RE: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise

On Mon, 6 Oct 2003, Hannu E K Nevalainen wrote: > > From: Igor Pechtchanski > > Sent: Monday, October 06, 2003 1:44 AM > > > It would be easy to check if the above was the reason for the hang by > > trying to call the following program from a postinstall script and seeing > > if it also hangs: > >

RE: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise

> From: Igor Pechtchanski > Sent: Monday, October 06, 2003 1:44 AM > It would be easy to check if the above was the reason for the hang by > trying to call the following program from a postinstall script and seeing > if it also hangs: It doesn't hang. :-I /Hannu E K Nevalainen, B.Sc. EE - 59?16.

RE: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise

s/Win200 SP4/Win2000 SP4/g -Original Message- From: Alan Miles [mailto:[EMAIL PROTECTED] Sent: October 5, 2003 20:41 To: [EMAIL PROTECTED] Subject: RE: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise All, Just to add another wrinkle: See

RE: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise

4, 2003 09:52 To: Cliff Hones Cc: [EMAIL PROTECTED] Subject: Re: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise On Sat, 4 Oct 2003, Cliff Hones wrote: > I ran cygcheck on cygpath, and was surprised to discover > that it has a dependence on ms

Re: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise

On Sun, 5 Oct 2003, Christopher Faylor wrote: > On Sun, Oct 05, 2003 at 07:43:53PM -0400, Igor Pechtchanski wrote: > >On Sat, 4 Oct 2003, Christopher Faylor wrote: > >>Who's going to find these functions? cygpath.exe is not going to > >>accidentally use ar function with the same name from another

Re: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise

On Sun, Oct 05, 2003 at 07:43:53PM -0400, Igor Pechtchanski wrote: >On Sat, 4 Oct 2003, Christopher Faylor wrote: >>Who's going to find these functions? cygpath.exe is not going to >>accidentally use ar function with the same name from another DLL. >>That's not how it works. msvcrt is being loade

Re: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise

On Sat, 4 Oct 2003, Christopher Faylor wrote: > On Sat, Oct 04, 2003 at 10:52:26AM -0400, Igor Pechtchanski wrote: > >On Sat, 4 Oct 2003, Cliff Hones wrote: > > > >> I ran cygcheck on cygpath, and was surprised to discover > >> that it has a dependence on msvcrt (as well as cygwin1): > >> > >> $ c

RE: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise

> From: Igor Pechtchanski > Sent: Sunday, October 05, 2003 9:48 PM > > I suspect you will see something different. I guess if on some Windows > > systems shlwapi.dll has a dependence on msvcrt.dll, it is not safe > > to call this from any cygwin app. > > > > -- Cliff > > Bingo. I think we have d

Re: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise

On Sat, 4 Oct 2003, Cliff Hones wrote: > Igor Pechtchanski wrote: > > > Oh, and this might explain why I'm not seeing the hang on my machine: > > > > $ cygcheck /bin/cygpath.exe > > C:/cygwin/bin/cygpath.exe > > C:/cygwin/bin\cygwin1.dll > > C:\WINNT\System32\KERNEL32.dll > > C:\WINNT\

<    1   2   3   4   >