rwho in cygwin?

rwho in cygwin?

[Christian Joensson]

Would it be possible/desirable to have the rwho package under cygwin?

Cheers,

/ChJ


--
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/

Re: rwho in cygwin?

[Corinna Vinschen]

On Tue, Oct 14, 2003 at 10:02:30AM +0200, Christian Joensson wrote:
> Would it be possible/desirable to have the rwho package under cygwin?

Did you try to build it?  Does it work?  Are you volunteering as a
package maintainer?  If so, then the answer is "yes".

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
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/

Re: rwho in cygwin?

[Christian Joensson]

On Tue, Oct 14, 2003 at 10:51:38AM +0200, Corinna Vinschen wrote:
> On Tue, Oct 14, 2003 at 10:02:30AM +0200, Christian Joensson wrote:
> > Would it be possible/desirable to have the rwho package under cygwin?
> 
> Did you try to build it?  Does it work?  Are you volunteering as a
> package maintainer?  If so, then the answer is "yes".

yes, no, not really... so as you put it, then "no".

Cheers,

/ChJ


--
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/

Re: rwho in cygwin?

[Carlo Florendo]

From: "Christian Joensson" 
> Would it be possible/desirable to have the rwho package under cygwin?

Yes. If someone would volunteer to contribute and maintain it.  

Thanks!

Best Regards,

Carlo
------
Carlo Florendo
Astra Philippines Inc.
http://www.hq.astra.ph
 



--
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/

cygpath hangings

[chris]

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 (because as previously noted 
the hang only occurs when running from setup.exe)

I used the basic setup contained in 
http://www.cygwin.com/ml/cygwin-apps/2003-10/msg00049.html , but made a 
new program I call cygcrash.cc, which I include the source code to at 
the end of this message. If I comment out the call to 
SHGetPathFromIDList in this program, the program returns, else it hangs.

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 shlobj.h), I'd be happy to do 
so, but won't unless it will be useful to someone :)

-- Code begins --

#include <shlobj.h>

void fee (void) {
  char *buf;
  LPITEMIDLIST id;
  SHGetPathFromIDList (id, buf);
}


int main (int argc, char **argv)
{
    return 0;
}



--
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/

Re: cygpath hangings

[Corinna Vinschen]

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 shlobj.h), I'd be happy to do 
> so, but won't unless it will be useful to someone :)
> 
> -- Code begins --
> 
> #include <shlobj.h>
> 
> void fee (void) {
>  char *buf;
>  LPITEMIDLIST id;
>  SHGetPathFromIDList (id, buf);
> }
> 
> 
> int main (int argc, char **argv)
> {
>    return 0;
> }

Nope, not for me.  Are you, by any chance, still using gcc2?

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
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/

Re: cygpath hangings

[chris]

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 the useless bits of shlobj.h), I'd be happy to do 
>>so, but won't unless it will be useful to someone :)
>>
>>-- Code begins --
>>
>>#include <shlobj.h>
>>
>>void fee (void) {
>> char *buf;
>> LPITEMIDLIST id;
>> SHGetPathFromIDList (id, buf);
>>}
>>
>>
>>int main (int argc, char **argv)
>>{
>>   return 0;
>>}
>>    
>>
>
>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 that you wouldn't have any problems with 
this, as it is just a (very!) cutdown cygpath.

Just checking (although sorry if I'm being stupid). Can someone else who 
is having the cygpath crash check they get a crash from this too?

Chris



--
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/

Re: cygpath hangings

[Corinna Vinschen]

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 that you wouldn't have any problems with 
> this, as it is just a (very!) cutdown cygpath.

No, I haven't.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
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/

Re: cygpath hangings

[Igor Pechtchanski]

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 (because as previously noted
> the hang only occurs when running from setup.exe)
>
> I used the basic setup contained in
> http://www.cygwin.com/ml/cygwin-apps/2003-10/msg00049.html , but made a
> new program I call cygcrash.cc, which I include the source code to at
> the end of this message. If I comment out the call to
> SHGetPathFromIDList in this program, the program returns, else it hangs.
>
> 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 shlobj.h), I'd be happy to do
> so, but won't unless it will be useful to someone :)
>
> -- Code begins --
>
> #include <shlobj.h>
>
> void fee (void) {
>   char *buf;
>   LPITEMIDLIST id;
>   SHGetPathFromIDList (id, buf);
> }
>
>
> int main (int argc, char **argv)
> {
>     return 0;
> }

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 SHGetPathFromIDList, call foo() from your fee() above, and link your
program against both test_dll.dll and SHLWAPI.DLL.
	Igor
P.S. Please don't start new threads as replies to unrelated messages -- it
confuses threaded readers.

-------------------------- BEGIN test_dll.c --------------------------
#include <windows.h>
#include <stdio.h>
#include <shlobj.h>

static FILE *output = NULL;

void SHGetPathFromIDList(LPITEMIDLIST id, char *buf) {
  return;
}

BOOL WINAPI DllMain(HINSTANCE h, DWORD f, LPVOID r) {
  if (!output) output = stderr;
  fprintf (output, "DLL loaded: ");
  switch (f) {
    case DLL_PROCESS_ATTACH: fprintf (output, "process attach");
                             break;
    case DLL_THREAD_ATTACH:  fprintf (output, "thread attach");
                             break;
    case DLL_THREAD_DETACH:  fprintf (output, "thread detach");
                             break;
    case DLL_PROCESS_DETACH: fprintf (output, "process detach");
                             break;
    default:                 fprintf (output, "WTF?!");
  }
  fprintf (output, "\n");
  fflush (output);
  return TRUE;
}
---------- Note: cutting here may damage your screen surface ---------

-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
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/

Re: cygpath hangings

[chris]

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 SHGetPathFromIDList, call foo() from your fee() above, and link your
>program against both test_dll.dll and SHLWAPI.DLL.
>	Igor
>P.S. Please don't start new threads as replies to unrelated messages -- it
>confuses threaded readers.
>  
>
Can I just ask (and I could be about to deeply embarass myself I think). 
How do I link against particular .dlls? up until now I've just been 
writing " gcc file.c -o file"



--
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/

Re: cygpath hangings

[Igor Pechtchanski]

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 something else (e.g., foo) that calls the
> >real SHGetPathFromIDList, call foo() from your fee() above, and link your
> >program against both test_dll.dll and SHLWAPI.DLL.
> >       Igor
> >P.S. Please don't start new threads as replies to unrelated messages -- it
> >confuses threaded readers.
>
> Can I just ask (and I could be about to deeply embarass myself I think).
> How do I link against particular .dlls? up until now I've just been
> writing "gcc file.c -o file"

"gcc file.c -o file -L. -ltest_dll"
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
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/

Re: cygpath hangings

[Brian Ford]

Igor,

On Tue, 14 Oct 2003, Igor Pechtchanski wrote:

> On Tue, 14 Oct 2003, chris wrote:
>
> > -- Code begins --
> >
> > #include <shlobj.h>
> >
> > void fee (void) {
> >   char *buf;
> >   LPITEMIDLIST id;
> >   SHGetPathFromIDList (id, buf);
> > }
> >
> > int main (int argc, char **argv)
> > {
> >     return 0;
> > }
>
> 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?
>
Yes, it still hangs when run under setup from explorer.  No output from
the hung one, or when run stand alone in bash.

> If it doesn't hang, try renaming
> SHGetPathFromIDList below to something else (e.g., foo) that calls the
> real SHGetPathFromIDList, call foo() from your fee() above, and link your
> program against both test_dll.dll and SHLWAPI.DLL.
>
Well, I didn't link explicitly with SHLWAPI.DLL, but same here.

There will be no ouput unless main calls foo, right?  Then, I still get a
hang under setup from explorer; no output.  Stand alone in a shell, output
is:

DLL loaded: process attach
DLL loaded: thread attach
Segmentation fault (core dumped)

The SEGV is expected given the code is invalid anyway.

Nothing to see here... move along...

>
> -------------------------- BEGIN test_dll.c --------------------------
> #include <windows.h>
> #include <stdio.h>
> #include <shlobj.h>
>
> static FILE *output = NULL;
>
> void SHGetPathFromIDList(LPITEMIDLIST id, char *buf) {
>   return;
> }
>
> BOOL WINAPI DllMain(HINSTANCE h, DWORD f, LPVOID r) {
>   if (!output) output = stderr;
>   fprintf (output, "DLL loaded: ");
>   switch (f) {
>     case DLL_PROCESS_ATTACH: fprintf (output, "process attach");
>                              break;
>     case DLL_THREAD_ATTACH:  fprintf (output, "thread attach");
>                              break;
>     case DLL_THREAD_DETACH:  fprintf (output, "thread detach");
>                              break;
>     case DLL_PROCESS_DETACH: fprintf (output, "process detach");
>                              break;
>     default:                 fprintf (output, "WTF?!");
>   }
>   fprintf (output, "\n");
>   fflush (output);
>   return TRUE;
> }
> ---------- Note: cutting here may damage your screen surface ---------

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

--
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/

Re: cygpath hangings

[Igor Pechtchanski]

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 <shlobj.h>
> > >
> > > void fee (void) {
> > >   char *buf;
> > >   LPITEMIDLIST id;
> > >   SHGetPathFromIDList (id, buf);
> > > }
> > >
> > > int main (int argc, char **argv)
> > > {
> > >     return 0;
> > > }
> >
> > 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?
> >
> Yes, it still hangs when run under setup from explorer.  No output from
> the hung one, or when run stand alone in bash.
>
> > If it doesn't hang, try renaming
> > SHGetPathFromIDList below to something else (e.g., foo) that calls the
> > real SHGetPathFromIDList, call foo() from your fee() above, and link your
> > program against both test_dll.dll and SHLWAPI.DLL.
> >
> Well, I didn't link explicitly with SHLWAPI.DLL, but same here.

Does "cygcheck yourprog.exe" show both test_dll.dll and SHLWAPI.DLL?

> 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...

> Then, I still get a hang under setup from explorer; no output.

This could be because the DLL was not loaded, or because of the two stdio
conflicts...  Did you compile the DLL with -mno-cygwin?

> Stand alone in a shell, output is:
>
> DLL loaded: process attach
> DLL loaded: thread attach
> Segmentation fault (core dumped)
>
> The SEGV is expected given the code is invalid anyway.
>
> Nothing to see here... move along...
> [snip test_dll.c]

Hmm.  Maybe if the DLL has exported global variables, not just functions?
I'll see if I can come up with the appropriate code and will then post it
to the list.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
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/

Re: cygpath hangings

[Brian Ford]

On Tue, 14 Oct 2003, Igor Pechtchanski wrote:
> Does "cygcheck yourprog.exe" show both test_dll.dll and SHLWAPI.DLL?
>
ford@fordpc ~
$ cygcheck cyghan.exe
Found: .\cyghan.exe
cyghan.exe
  G:\cygwin\bin\cygwin1.dll
    D:\WINNT\System32\KERNEL32.dll
      D:\WINNT\System32\ntdll.dll
  .\cygl.dll
    D:\WINNT\System32\SHELL32.DLL
      D:\WINNT\System32\GDI32.dll
        D:\WINNT\System32\USER32.dll
          D:\WINNT\System32\ADVAPI32.dll
            D:\WINNT\System32\RPCRT4.dll
      D:\WINNT\System32\SHLWAPI.dll
        D:\WINNT\System32\msvcrt.dll
      D:\WINNT\System32\COMCTL32.dll

test_dll.dll is actually .\cygl.dll

>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 load, or is it the first referance?  I'm a DLL
dunce.

> > Then, I still get a hang under setup from explorer; no output.
>
> This could be because the DLL was not loaded, or because of the two stdio
> conflicts...  Did you compile the DLL with -mno-cygwin?
>
No.  I guess you wanted me too? :)

> > Stand alone in a shell, output is:
> >
> > DLL loaded: process attach
> > DLL loaded: thread attach
> > Segmentation fault (core dumped)
> >
> > The SEGV is expected given the code is invalid anyway.
> >
> > Nothing to see here... move along...
> > [snip test_dll.c]
>
> Hmm.  Maybe if the DLL has exported global variables, not just functions?
> I'll see if I can come up with the appropriate code and will then post it
> to the list.
>
Not following, but ok.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

--
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/

Re: cygpath hangings

[Igor Pechtchanski]

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 load, or is it the first referance?  I'm a DLL
> dunce.

I've just verified that the DLL is loaded even if no functions from it are
called (or variables referenced).  FWIW, here's the code I used:

$ cat > cpath.c
int hello();
void foo (void) { hello(); }
int main (int argc, char **argv) { return 0; }
$ cat > cygx.c
#include <windows.h>
#include <stdio.h>

static int counter = 0;
static FILE *output = NULL;

int hello() {
  fprintf (output, "Hello world for the %dth time!\n", counter);
  fflush (output);
  return counter++;
}

BOOL WINAPI DllMain(HINSTANCE h, DWORD f, LPVOID r) {
  if (!output) output = fopen("cygx.out", "wt");
  fprintf (output, "DLL loaded: ");
  switch (f) {
    case DLL_PROCESS_ATTACH: fprintf (output, "process attach");
                             break;
    case DLL_THREAD_ATTACH:  fprintf (output, "thread attach");
                             break;
    case DLL_THREAD_DETACH:  fprintf (output, "thread detach");
                             break;
    case DLL_PROCESS_DETACH: fprintf (output, "process detach");
                             break;
    default:                 fprintf (output, "WTF?!");
  }
  fprintf (output, "\n");
  fflush (output);
  return TRUE;
}
$ gcc -mno-cygwin -shared -o cygx.dll cygx.c
$ gcc -o cpath.exe cpath.c -L. -lcygx
$ ./cpath.exe; cat cygx.out
DLL loaded: process attach
DLL loaded: thread attach
DLL loaded: process detach
$

> > > Then, I still get a hang under setup from explorer; no output.
> >
> > This could be because the DLL was not loaded, or because of the two stdio
> > conflicts...  Did you compile the DLL with -mno-cygwin?
>
> No.  I guess you wanted me too? :)

I don't know if it matters, frankly.  It looks like the DLL is loaded, but
it doesn't load completely.  Maybe something that SHLWAPI.DLL is doing on
initialization?

> > > Stand alone in a shell, output is:
> > >
> > > DLL loaded: process attach
> > > DLL loaded: thread attach
> > > Segmentation fault (core dumped)
> > >
> > > The SEGV is expected given the code is invalid anyway.
> > >
> > > Nothing to see here... move along...
> > > [snip test_dll.c]
> >
> > Hmm.  Maybe if the DLL has exported global variables, not just functions?
> > I'll see if I can come up with the appropriate code and will then post it
> > to the list.
> >
> Not following, but ok.

I meant making "counter" in the above example global rather than static.
Turns out it doesn't make a difference -- the DLL is loaded anyway.  I
still suspect the initialization code in SHLWAPI.DLL is doing something
that Cygwin doesn't like.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
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/

Re: cygpath hangings

[Brian Ford]

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 foo isn't
> > > called...
> > >
> > Just linking to it causes a load, or is it the first referance?  I'm a DLL
> > dunce.
>
> I've just verified that the DLL is loaded even if no functions from it are
> called (or variables referenced).  FWIW, here's the code I used:
>
It has been a while since I ran through this stuff, but I did get that
output in a bash shell after compiling with -mno-cygwin (I think).

> > > > Then, I still get a hang under setup from explorer; no output.
> > >
> > > This could be because the DLL was not loaded, or because of the two stdio
> > > conflicts...  Did you compile the DLL with -mno-cygwin?
> >
> > No.  I guess you wanted me too? :)
>
> I don't know if it matters, frankly.  It looks like the DLL is loaded, but
> it doesn't load completely.  Maybe something that SHLWAPI.DLL is doing on
> initialization?
>
I think it might (again, going on my faulty memory).

Does that comment mean you can reproduce this now?  I guess you're just
talking about email observations, right.

> I still suspect the initialization code in SHLWAPI.DLL is doing
> something that Cygwin doesn't like.
>
Maybe, it is just *very* strange.

Only setup launched from explorer launched bash launched back tick SHLWAPI
base program without input redirection.  Ugh...!  Any change in the above
and the problem goes away. (ie. explorer->setup->bash`SHLWAPI exe #
without < /dev/null`).

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

--
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/

Re: cygpath hangings

[Brian Ford]

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 the hang regardless.

> -- Code begins --
>
> #include <shlobj.h>
>
> void fee (void) {
>   char *buf;
>
I changed this to char buf[255] just to be safer.

>   LPITEMIDLIST id;
>   SHGetPathFromIDList (id, buf);
> }
>
> int main (int argc, char **argv)
> {
>     return 0;
> }
>

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

--
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/

Re: cygpath hangings

[Brian Ford]

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, all is fine. In g++, it hangs.
> >
> Really?  I see the hang regardless.
>
It is also valid -mno-cygwin code, and when compiled this way, it still
hangs.  Doesn't this eliminate a good portion of the Cygwin startup code
since this is a MINGW executable?

It must be something the exec stub did?  I do see a few cases of suspended
starting in spawn_guts.  Might it have forgotten to resume?  Is there an
easy way to tell if it is suspended?

I'm still puzzled about why the input redirect helps.  Recap:

/etc/postinstall/hang.sh:

#!/bin/bash

FOO=`hangprog.exe < /dev/null`
BAR=`hangprog.exe` # hangs here!

where hangprog.exe is:

> > -- Code begins --
> >
> > #include <shlobj.h>
> >
> > void fee (void) {
> >   char *buf;
> >
> I changed this to char buf[255] just to be safer.
>
> >   LPITEMIDLIST id;
> >   SHGetPathFromIDList (id, buf); // Comment this out and no hang.
> > }
> >
> > int main (int argc, char **argv)
> > {
> >     return 0;
> > }
> >

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

--
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/

RE: cygpath hangings

[Steve Fairbairn]

> 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 checking... have you been suffering from the "cygpath" crashing 
> during setup? If not I imagine that you wouldn't have any 
> problems with 
> this, as it is just a (very!) cutdown cygpath.
> 
> Just checking (although sorry if I'm being stupid). Can 
> someone else who 
> is having the cygpath crash check they get a crash from this too?
> 

Chris & All,

I dare say Corinna has a fair idea of what the code is, and whether she has
experienced the hanging problems ;).

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 a description of how to make setup run it (as I've not
actually gleaned that information from the mails on the subject), I will be
glad to see if I can cause the issue to happen.

I am currently getting the cygwin sources out of cvs, but due to work
firewall being quite strict I'm having to get them via an ssh tunnel to my
home server (ADSL) so could be quite some time.  Does anyone know if I want
to update my gcc before attempting to build the DLL with debug on (gcc
version 3.2 20020927 (prerelease))?

Cheers,

Steve Fairbairn.
-- 
-- LONG DISCLAIMER --

******************************************************* 
This email has originated from Perwill plc (Registration No. 1906964) 
Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK 
Tel: +44 (0)1420 545000 
Fax: +44 (0)1420 545001 
www.perwill.com 
******************************************************* 
Privileged, confidential and/or copyright information may be contained 
in this email, and is only for the use of the intended addressee. 
To copy, forward, disclose or otherwise use it in any way if you are not 
the intended recipient or responsible for delivering to him/her is
prohibited.
If you receive this email by mistake, please advise the sender immediately, 
by using the reply facility in your email software.

We may monitor the content of emails sent and received via our network 
for the purposes of ensuring compliance with policies and procedures. 
This message is subject to and does not create or vary any contractual 
relationships between Perwill plc and the recipient. 
******************************************************* 
Any opinions expressed in the email are those of the sender and not 
necessarily of Perwill plc.
******************************************************* 
This email has been scanned for known viruses using 
McAfee WebShield 4.5 MR1a 
******************************************************* 



--
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/

RE: cygpath hangings

[Igor Pechtchanski]

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 a description of how to make setup run it (as I've not
> actually gleaned that information from the mails on the subject), I will be
> glad to see if I can cause the issue to happen.

Steve,

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
to call it through bash, too), put it in /etc/postinstall, and run setup
in "Keep" mode.  The script will be run during the postinstall phase (even
though you won't install anything).
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
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/

Re: cygpath hangings

[Cliff Hones]

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 approaches could be worthwhile.

We seem to be looking for a subtle difference in the environment
between a hanging postinstall script (which happens on some
systems only, and also only when setup is executed from an
explorer window) and a working one.  Is it possible cygcheck
might show such a difference, or is there another utility
which could show system info (such as some of the current
internal state of the cygwin shared memory)?  Running
cygcheck -vs (and/or some other such utility) from
a hanging and non-hanging postinstall shell might come
up with something.

-- Cliff


--
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/

RE: cygpath hangings

[Hannu E K Nevalainen]

> 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
> to call it through bash, too), put it in /etc/postinstall, and run setup
> in "Keep" mode.  The script will be run during the postinstall phase (even
> though you won't install anything).
> 	Igor

In addition to what is above...
I've been using these to generate the problem. HTH.

--
$ cat /etc/postinstall/t3.sh
#!/bin/bash -x

# CYGWIN_DEBUG=/bin/cygpath
# set CYGWIN_SLEEP=20000

echo -e "CYGWIN_DEBUG=${CYGWIN_DEBUG}\tCYGWIN_SLEEP=${CYGWIN_SLEEP}"

TOPFOLDER="$(cygpath -A -P)/Cygwin-XFree86"
echo $TOPFOLDER


$ cat ~/scripts/t3
#!/bin/bash

if [ -f /etc/postinstall/t3.sh.done ] ; then
  mv /etc/postinstall/t3.sh.done /etc/postinstall/t3.sh
fi

cygstart -- /install/setup.exe --no-md5



/Hannu E K Nevalainen, B.Sc. EE - 59?16.37'N, 17?12.60'E
-- UTC+01, DST -> UTC+02  --
--END OF MESSAGE--


--
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/

RE: cygpath hangings

[Steve Fairbairn]

> -----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/postinstall that runs cygcheck -vs to a file,
and send that in?

Steve.
-- 
-- LONG DISCLAIMER --

******************************************************* 
This email has originated from Perwill plc (Registration No. 1906964) 
Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK 
Tel: +44 (0)1420 545000 
Fax: +44 (0)1420 545001 
www.perwill.com 
******************************************************* 
Privileged, confidential and/or copyright information may be contained 
in this email, and is only for the use of the intended addressee. 
To copy, forward, disclose or otherwise use it in any way if you are not 
the intended recipient or responsible for delivering to him/her is
prohibited.
If you receive this email by mistake, please advise the sender immediately, 
by using the reply facility in your email software.

We may monitor the content of emails sent and received via our network 
for the purposes of ensuring compliance with policies and procedures. 
This message is subject to and does not create or vary any contractual 
relationships between Perwill plc and the recipient. 
******************************************************* 
Any opinions expressed in the email are those of the sender and not 
necessarily of Perwill plc.
******************************************************* 
This email has been scanned for known viruses using 
McAfee WebShield 4.5 MR1a 
******************************************************* 



--
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/

Re: cygpath hangings

[chris]

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/postinstall that runs cygcheck -vs to a file,
>and send that in?
>
>Steve.
>  
>
Your wish is my command :) Unfortunatly, whatever is causing the hanging 
bug is also hanging cygcheck :(

I'll attach what I get anyway.. I'm running the following script:

#!/bin/bash -x

which which
cygpath -S
cygcheck -vs
FII=$(which which)
FOO=$(cygcheck -vs)

--- setup.log.postinstall follows ---
+ which which
/usr/bin/which
+ cygpath -S
+ cygcheck -vs

Cygwin Win95/NT Configuration Diagnostics
Current System Time: Tue Oct 14 15:29:49 2003

Windows 2000 Professional Ver 5.0 Build 2195 Service Pack 4

Path:    F:\cygwin\bin
    F:\cygwin\bin
    F:\cygwin\bin
    F:\cygwin\bin
    c:\WINNT\system32
    c:\WINNT
    c:\WINNT\System32\Wbem
    c:\texmf\miktex\bin
    c:\Program Files\MiKTeX\miktex\bin
    F:\cygwin\bin
    c:\j2sdk1.4.1\bin
    f:\eclipse\lib\i386_nt
    F:\cygwin\bin

Output from F:\cygwin\bin\id.exe (nontsec)
UID: 11724(caj) GID: 10513(mkgroup_l_d)
10513(mkgroup_l_d)

Output from F:\cygwin\bin\id.exe (ntsec)
UID: 11724(caj) GID: 10513(mkgroup_l_d)
547(Power Users)    545(Users)         
10513(mkgroup_l_d)

SysDir: C:\WINNT\system32
WinDir: C:\WINNT

HOME = `c:\'
PWD = `/'

ALLUSERSPROFILE = `C:\Documents and Settings\All Users'
APPDATA = `C:\Documents and Settings\caj\Application Data'
COMMONPROGRAMFILES = `C:\Program Files\Common Files'
COMPUTERNAME = `PC302'
COMSPEC = `C:\WINNT\system32\cmd.exe'
CYGWINROOT = `F:\cygwin'
HOMEDRIVE = `C:'
HOMEPATH = `\'
LOGONSERVER = `\\OUSE'
NUMBER_OF_PROCESSORS = `1'
OS2LIBPATH = `C:\WINNT\system32\os2\dll;'
OS = `Windows_NT'
PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH'
PROCESSOR_ARCHITECTURE = `x86'
PROCESSOR_IDENTIFIER = `x86 Family 6 Model 6 Stepping 2, AuthenticAMD'
PROCESSOR_LEVEL = `6'
PROCESSOR_REVISION = `0602'
PROGRAMFILES = `C:\Program Files'
SHLVL = `1'
SMS_LOCAL_DIR = `C:\WINNT'
SMS_LOCAL_DIR_USER = `C:\WINNT'
SYSTEMDRIVE = `C:'
SYSTEMROOT = `C:\WINNT'
TEMP = `c:\DOCUME~1\caj\LOCALS~1\Temp'
TERM = `cygwin'
TMP = `c:\DOCUME~1\caj\LOCALS~1\Temp'
USERDNSDOMAIN = `ad.cs.york.ac.uk'
USERDOMAIN = `AD'
USERNAME = `caj'
USERPROFILE = `C:\Documents and Settings\caj'
WINDIR = `C:\WINNT'
_ = `/usr/bin/cygcheck'

Use `-r' to scan registry

a:  fd           N/A    N/A                   
c:  hd  NTFS    5004Mb  59% CP CS UN PA FC    
d:  fd           N/A    N/A                   
e:  cd           N/A    N/A                   
f:  hd  NTFS   13641Mb  41% CP CS UN PA FC    
h:  net NTFS   16132Mb  63% CP CS    PA        caj
w:  net NTFS       5Mb  32% CP CS    PA        caj
z:  net NTFS   16132Mb  92% CP CS    PA        software

F:\cygwin      /          user    binmode
F:\cygwin/bin  /usr/bin   user    binmode
F:\cygwin/lib  /usr/lib   user    binmode
.              /cygdrive  user    binmode,cygdrive

Found: F:\cygwin\bin\awk.exe
Found: F:\cygwin\bin\bash.exe
Found: F:\cygwin\bin\cat.exe
Found: F:\cygwin\bin\cp.exe
Found: F:\cygwin\bin\cpp.exe
Found: F:\cygwin\bin\find.exe
Found: F:\cygwin\bin\gcc.exe
Found: F:\cygwin\bin\gdb.exe
Found: F:\cygwin\bin\grep.exe
Found: F:\cygwin\bin\ld.exe
Found: F:\cygwin\bin\ls.exe
Found: F:\cygwin\bin\make.exe
Found: F:\cygwin\bin\mv.exe
Found: F:\cygwin\bin\rm.exe
Found: F:\cygwin\bin\sed.exe
Found: F:\cygwin\bin\sh.exe
Found: F:\cygwin\bin\tar.exe

  802k 2003/09/15 F:\cygwin\bin\cygaspell-15.dll - os=4.0 img=1.0 sys=4.0
                  "cygaspell-15.dll" v0.0 ts=2003/9/15 13:32
   61k 2003/08/09 F:\cygwin\bin\cygbz2-1.dll - os=4.0 img=1.0 sys=4.0
                  "cygbz2-1.dll" v0.0 ts=2003/8/9 7:35
  842k 2003/09/30 F:\cygwin\bin\cygcrypto-0.9.7.dll - os=4.0 img=1.0 sys=4.0
                  "cygcrypto-0.9.7.dll" v0.0 ts=2003/9/30 17:49
  645k 2003/04/11 F:\cygwin\bin\cygcrypto.dll - os=4.0 img=1.0 sys=4.0
                  "cygcrypto.dll" v0.0 ts=2003/4/11 11:37
   28k 2003/08/11 F:\cygwin\bin\cygcygipc-2.dll - os=4.0 img=1.0 sys=4.0
                  "cygcygipc-2.dll" v0.0 ts=2003/8/11 1:54
  380k 2002/07/24 F:\cygwin\bin\cygdb-3.1.dll - os=4.0 img=1.0 sys=4.0
                  "cygdb-3.1.dll" v0.0 ts=2002/7/24 17:24
  487k 2002/07/24 F:\cygwin\bin\cygdb_cxx-3.1.dll - os=4.0 img=1.0 sys=4.0
                  "cygdb_cxx-3.1.dll" v0.0 ts=2002/7/24 17:25
  132k 2003/07/12 F:\cygwin\bin\cygexpat-0.dll - os=4.0 img=1.0 sys=4.0
                  "cygexpat-0.dll" v0.0 ts=2003/7/12 12:33
   45k 2001/04/25 F:\cygwin\bin\cygform5.dll - os=4.0 img=1.0 sys=4.0
                  "cygform5.dll" v0.0 ts=2001/4/25 6:28
   35k 2002/01/09 F:\cygwin\bin\cygform6.dll - os=4.0 img=1.0 sys=4.0
                  "cygform6.dll" v0.0 ts=2002/1/9 6:03
   48k 2003/08/09 F:\cygwin\bin\cygform7.dll - os=4.0 img=1.0 sys=4.0
                  "cygform7.dll" v0.0 ts=2003/8/9 10:25
   28k 2003/07/20 F:\cygwin\bin\cyggdbm-3.dll - os=4.0 img=1.0 sys=4.0
                  "cyggdbm-3.dll" v0.0 ts=2003/7/20 8:58
   30k 2003/08/11 F:\cygwin\bin\cyggdbm-4.dll - os=4.0 img=1.0 sys=4.0
                  "cyggdbm-4.dll" v0.0 ts=2003/8/11 3:12
   19k 2003/03/22 F:\cygwin\bin\cyggdbm.dll - os=4.0 img=1.0 sys=4.0
                  "cyggdbm.dll" v0.0 ts=2002/2/20 3:05
   15k 2003/07/20 F:\cygwin\bin\cyggdbm_compat-3.dll - os=4.0 img=1.0 
sys=4.0
                  "cyggdbm_compat-3.dll" v0.0 ts=2003/7/20 9:00
   15k 2003/08/11 F:\cygwin\bin\cyggdbm_compat-4.dll - os=4.0 img=1.0 
sys=4.0
                  "cyggdbm_compat-4.dll" v0.0 ts=2003/8/11 3:13
   69k 2003/08/10 F:\cygwin\bin\cyggettextlib-0-12-1.dll - os=4.0 
img=1.0 sys=4.0
                  "cyggettextlib-0-12-1.dll" v0.0 ts=2003/8/10 23:10
   12k 2003/08/10 F:\cygwin\bin\cyggettextpo-0.dll - os=4.0 img=1.0 sys=4.0
                  "cyggettextpo-0.dll" v0.0 ts=2003/8/10 23:11
  134k 2003/08/10 F:\cygwin\bin\cyggettextsrc-0-12-1.dll - os=4.0 
img=1.0 sys=4.0
                  "cyggettextsrc-0-12-1.dll" v0.0 ts=2003/8/10 23:10
   17k 2001/06/28 F:\cygwin\bin\cyghistory4.dll - os=4.0 img=1.0 sys=4.0
                  "cyghistory4.dll" v0.0 ts=2001/1/7 4:34
   29k 2003/08/10 F:\cygwin\bin\cyghistory5.dll - os=4.0 img=1.0 sys=4.0
                  "cyghistory5.dll" v0.0 ts=2003/8/11 0:16
  958k 2003/08/10 F:\cygwin\bin\cygiconv-2.dll - os=4.0 img=1.0 sys=4.0
                  "cygiconv-2.dll" v0.0 ts=2003/8/10 21:57
   22k 2001/12/13 F:\cygwin\bin\cygintl-1.dll - os=4.0 img=1.0 sys=4.0
                  "cygintl-1.dll" v0.0 ts=2001/12/13 9:28
   37k 2003/08/10 F:\cygwin\bin\cygintl-2.dll - os=4.0 img=1.0 sys=4.0
                  "cygintl-2.dll" v0.0 ts=2003/8/10 22:50
   21k 2001/06/20 F:\cygwin\bin\cygintl.dll - os=4.0 img=1.0 sys=4.0
                  "cygintl.dll" v0.0 ts=2001/6/20 18:09
  132k 2003/08/11 F:\cygwin\bin\cygjpeg-62.dll - os=4.0 img=1.0 sys=4.0
                  "cygjpeg-62.dll" v0.0 ts=2003/8/11 1:37
  119k 2002/02/09 F:\cygwin\bin\cygjpeg6b.dll - os=4.0 img=1.0 sys=4.0
                  "cygjpeg6b.dll" v0.0 ts=2002/2/9 5:19
   26k 2001/04/25 F:\cygwin\bin\cygmenu5.dll - os=4.0 img=1.0 sys=4.0
                  "cygmenu5.dll" v0.0 ts=2001/4/25 6:27
   20k 2002/01/09 F:\cygwin\bin\cygmenu6.dll - os=4.0 img=1.0 sys=4.0
                  "cygmenu6.dll" v0.0 ts=2002/1/9 6:03
   29k 2003/08/09 F:\cygwin\bin\cygmenu7.dll - os=4.0 img=1.0 sys=4.0
                  "cygmenu7.dll" v0.0 ts=2003/8/9 10:25
  453k 2003/07/27 F:\cygwin\bin\cygnaim_core-0.dll - os=4.0 img=1.0 sys=4.0
                  "cygnaim_core-0.dll" v0.0 ts=2003/7/27 6:46
  156k 2001/04/25 F:\cygwin\bin\cygncurses++5.dll - os=4.0 img=1.0 sys=4.0
                  "cygncurses++5.dll" v0.0 ts=2001/4/25 6:29
  175k 2002/01/09 F:\cygwin\bin\cygncurses++6.dll - os=4.0 img=1.0 sys=4.0
                  "cygncurses++6.dll" v0.0 ts=2002/1/9 6:03
  226k 2001/04/25 F:\cygwin\bin\cygncurses5.dll - os=4.0 img=1.0 sys=4.0
                  "cygncurses5.dll" v0.0 ts=2001/4/25 6:17
  202k 2002/01/09 F:\cygwin\bin\cygncurses6.dll - os=4.0 img=1.0 sys=4.0
                  "cygncurses6.dll" v0.0 ts=2002/1/9 6:03
  224k 2003/08/09 F:\cygwin\bin\cygncurses7.dll - os=4.0 img=1.0 sys=4.0
                  "cygncurses7.dll" v0.0 ts=2003/8/9 10:24
   15k 2001/04/25 F:\cygwin\bin\cygpanel5.dll - os=4.0 img=1.0 sys=4.0
                  "cygpanel5.dll" v0.0 ts=2001/4/25 6:27
   12k 2002/01/09 F:\cygwin\bin\cygpanel6.dll - os=4.0 img=1.0 sys=4.0
                  "cygpanel6.dll" v0.0 ts=2002/1/9 6:03
   19k 2003/08/09 F:\cygwin\bin\cygpanel7.dll - os=4.0 img=1.0 sys=4.0
                  "cygpanel7.dll" v0.0 ts=2003/8/9 10:24
   67k 2003/09/10 F:\cygwin\bin\cygpcre-0.dll - os=4.0 img=1.0 sys=4.0
                  "cygpcre-0.dll" v0.0 ts=2003/9/10 15:25
   63k 2003/04/11 F:\cygwin\bin\cygpcre.dll - os=4.0 img=1.0 sys=4.0
                  "cygpcre.dll" v0.0 ts=2003/4/11 9:31
   15k 2003/09/10 F:\cygwin\bin\cygpcreposix-0.dll - os=4.0 img=1.0 sys=4.0
                  "cygpcreposix-0.dll" v0.0 ts=2003/9/10 15:25
   61k 2003/04/11 F:\cygwin\bin\cygpcreposix.dll - os=4.0 img=1.0 sys=4.0
                  "cygpcreposix.dll" v0.0 ts=2003/4/11 9:31
 1100k 2003/08/29 F:\cygwin\bin\cygperl5_8_0.dll - os=4.0 img=1.0 sys=4.0
                  "cygperl5_8_0.dll" v0.0 ts=2003/8/29 11:20
  168k 2003/08/10 F:\cygwin\bin\cygpng10.dll - os=4.0 img=1.0 sys=4.0
                  "cygpng10.dll" v0.0 ts=2003/8/10 23:31
  173k 2003/08/10 F:\cygwin\bin\cygpng12.dll - os=4.0 img=1.0 sys=4.0
                  "cygpng12.dll" v0.0 ts=2003/8/10 23:35
  170k 2002/01/21 F:\cygwin\bin\cygpng2.dll - os=4.0 img=1.0 sys=4.0
                  "cygpng2.dll" v0.0 ts=2002/1/21 1:05
   22k 2002/06/09 F:\cygwin\bin\cygpopt-0.dll - os=4.0 img=1.0 sys=4.0
                  "cygpopt-0.dll" v0.0 ts=2002/6/9 6:45
  108k 2001/06/28 F:\cygwin\bin\cygreadline4.dll - os=4.0 img=1.0 sys=4.0
                  "cygreadline4.dll" v0.0 ts=2001/1/7 4:34
  148k 2003/08/10 F:\cygwin\bin\cygreadline5.dll - os=4.0 img=1.0 sys=4.0
                  "cygreadline5.dll" v0.0 ts=2003/8/11 0:16
  171k 2003/09/30 F:\cygwin\bin\cygssl-0.9.7.dll - os=4.0 img=1.0 sys=4.0
                  "cygssl-0.9.7.dll" v0.0 ts=2003/9/30 17:49
  165k 2003/04/11 F:\cygwin\bin\cygssl.dll - os=4.0 img=1.0 sys=4.0
                  "cygssl.dll" v0.0 ts=2003/4/11 11:37
  281k 2003/02/24 F:\cygwin\bin\cygtiff3.dll - os=4.0 img=1.0 sys=4.0
                  "cygtiff3.dll" v0.0 ts=2003/2/24 4:58
  282k 2003/08/11 F:\cygwin\bin\cygtiff4.dll - os=4.0 img=1.0 sys=4.0
                  "cygtiff4.dll" v0.0 ts=2003/8/11 3:32
   50k 2003/08/09 F:\cygwin\bin\cygXpm-noX4.dll - os=4.0 img=1.0 sys=4.0
                  "cygXpm-noX4.dll" v0.0 ts=2003/8/9 8:21
   54k 2003/08/09 F:\cygwin\bin\cygXpm-X4.dll - os=4.0 img=1.0 sys=4.0
                  "cygXpm-X4.dll" v0.0 ts=2003/8/9 8:22
   60k 2003/08/09 F:\cygwin\bin\cygz.dll - os=4.0 img=1.0 sys=4.0
                  "cygz.dll" v0.0 ts=2003/8/9 7:28
  949k 2003/09/20 F:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
                  "cygwin1.dll" v0.0 ts=2003/9/20 21:31
    Cygwin DLL version info:
        DLL version: 1.5.5
        DLL epoch: 19
        DLL bad signal mask: 19005
        DLL old termios: 5
        DLL malloc env: 28
        API major: 0
        API minor: 94
        Shared data: 3
        DLL identifier: cygwin1
        Mount registry: 2
        Cygnus registry name: Cygnus Solutions
        Cygwin registry name: Cygwin
        Program options name: Program Options
        Cygwin mount registry name: mounts v2
        Cygdrive flags: cygdrive flags
        Cygdrive prefix: cygdrive prefix
        Cygdrive default prefix:
        Build date: Sat Sep 20 16:31:15 EDT 2003
        CVS tag: cr-0x9b
        Shared id: cygwin1S3


Cygwin Package Information
Last downloaded files to: f:\temp
Last downloaded files from: 
ftp://ftp.mirror.ac.uk/sites/sources.redhat.com/pub/cygwin

Package              Version           
_update-info-dir     00221-1           
a2ps                 4.13-1            
ash                  20031007-1        
aspell               0.50.3-1          
aspell-dev           0.50.3-1          
aspell-doc           0.50.3-1          
aspell-en            0.51.0-1          
autoconf             2.57a-1           
autoconf-devel       2.57-2            
autoconf-stable      2.13-5            
automake             1.7.5a-1          
automake-devel       1.7.6-2           
automake-stable      1.4p5-6           
base-files           2.6-1             
base-passwd          1.1-1             
bash                 2.05b-15          
binutils             20030901-1        
bzip2                1.0.2-5           
cygipc               2.01-2            
cygrunsrv            0.96-2            
cygutils             1.2.1-2           
cygwin               1.5.5-1           
diffutils            2.8.4-1           
editrights           1.01-1            
expat                1.95.6-2          
fileutils            4.1-2             
findutils            4.1.7-4           
gawk                 3.1.3-3           
gcc                  3.3.1-2           
gcc-mingw            20030911-3        
gcc2                 2.95.3-10         
gdb                  20030919-1        
gdbm                 1.8.3-7           
gettext              0.12.1-3          
ghostscript          7.05-2            
ghostscript-base     7.05-2            
gnugo                3.4-1             
grep                 2.5-1             
groff                1.18.1-2          
gzip                 1.3.5-1           
less                 381-1             
libaspell15          0.50.3-1          
libbz2_1             1.0.2-5           
libdb3.1             3.1.17-2          
libgdbm              1.8.0-5           
libgdbm-devel        1.8.3-7           
libgdbm3             1.8.3-3           
libgdbm4             1.8.3-7           
libgettextpo0        0.12.1-3          
libiconv2            1.9.1-3           
libintl              0.10.38-3         
libintl1             0.10.40-1         
libintl2             0.12.1-3          
libjpeg62            6b-11             
libjpeg6b            6b-8              
libncurses5          5.2-1             
libncurses6          5.2-8             
libncurses7          5.3-4             
libpcre              4.1-1             
libpcre0             4.4-2             
libpng               1.2.5-4           
libpng10             1.0.15-4          
libpng10-devel       1.0.15-4          
libpng12             1.2.5-4           
libpng12-devel       1.2.5-4           
libpng2              1.0.12-1          
libpopt0             1.6.4-4           
libreadline4         4.1-2             
libreadline5         4.3-5             
libtiff-devel        3.6.0-5           
libtiff3             3.6.0-2           
libtiff4             3.6.0-5           
login                1.9-7             
lynx                 2.8.4-7           
m4                   1.4-1             
make                 3.80-1            
man                  1.5j-2            
mingw-runtime        3.2-1             
mktemp               1.5-3             
ncurses              5.3-4             
openssh              3.7.1p2-1         
openssl              0.9.7c-1          
pcre                 4.4-2             
pcre-doc             4.4-2             
perl                 5.8.0-5           
psutils              1.17-1            
readline             4.3-5             
rsync                2.5.6-2           
rxvt                 2.7.10-3          
sed                  4.0.7-3           
sh-utils             2.0.15-4          
tar                  1.13.25-3         
tcltk                20030901-1        
termcap              20021106-2        
terminfo             5.3_20030726-1    
texinfo              4.2-4             
textutils            2.0.21-1          
upx                  1.24-1            
w32api               2.4-1             
which                1.5-2             
zlib                 1.1.4-4           
Use -h to see help about each section
++ which which
+ FII=/usr/bin/which
++ cygcheck -vs



--
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/

Re: cygpath hangings

[Cliff Hones]

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.  I'm not too hopeful
though!

-- Cliff


--
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/

RE: cygpath hangings

[Steve Fairbairn]

[-- Attachment #1: Type: text/plain, Size: 2675 bytes --]


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.

---
$ cat setup_from_win.sh.done 
#!/bin/bash -x

# CYGWIN_DEBUG=/bin/cygpath
# set CYGWIN_SLEEP=20000

echo $PATH > /cygdrive/d/path_from_setup
---

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 they are as well because of the contents of
one of them, but here is what I see.

---
Steve Fairbairn@stevefnec /cygdrive/d
$ cat path_from_normal 
/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/cygdrive/d/v80003/data/work/use
rbin:/cygdrive/d/v80003/bin:/cygdrive/c/Program
Files/j2sdk1.4.2_01/bin:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cy
gdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/Program Files/Microsoft Visual
Studio/VC98/Bin:/usr/bin
---

---
Steve Fairbairn@stevefnec /cygdrive/d
$ cat path_from_setup 
/usr/bin:/usr/bin:/usr/bin:/usr/bin:ÓD-w@3"
---

Could this be something to do with it all?

Steve.
-- 
-- LONG DISCLAIMER --

******************************************************* 
This email has originated from Perwill plc (Registration No. 1906964) 
Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK 
Tel: +44 (0)1420 545000 
Fax: +44 (0)1420 545001 
www.perwill.com 
******************************************************* 
Privileged, confidential and/or copyright information may be contained 
in this email, and is only for the use of the intended addressee. 
To copy, forward, disclose or otherwise use it in any way if you are not 
the intended recipient or responsible for delivering to him/her is
prohibited.
If you receive this email by mistake, please advise the sender immediately, 
by using the reply facility in your email software.

We may monitor the content of emails sent and received via our network 
for the purposes of ensuring compliance with policies and procedures. 
This message is subject to and does not create or vary any contractual 
relationships between Perwill plc and the recipient. 
******************************************************* 
Any opinions expressed in the email are those of the sender and not 
necessarily of Perwill plc.
******************************************************* 
This email has been scanned for known viruses using 
McAfee WebShield 4.5 MR1a 
******************************************************* 


    


[-- Attachment #2: path_from_normal --]
[-- Type: application/octet-stream, Size: 300 bytes --]

/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/cygdrive/d/v80003/data/work/userbin:/cygdrive/d/v80003/bin:/cygdrive/c/Program Files/j2sdk1.4.2_01/bin:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/Program Files/Microsoft Visual Studio/VC98/Bin:/usr/bin

[-- Attachment #3: path_from_setup --]
[-- Type: application/octet-stream, Size: 47 bytes --]

[-- Attachment #4: Type: text/plain, Size: 218 bytes --]

--
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/

Re: cygpath hangings

[Christopher Faylor]

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 with the path being
>different, so I thought I'd run a quick test.
>
>---
>$ cat setup_from_win.sh.done 
>#!/bin/bash -x
>
># CYGWIN_DEBUG=/bin/cygpath
># set CYGWIN_SLEEP=20000
>
>echo $PATH > /cygdrive/d/path_from_setup
>---
>
>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 they are as well because of the contents of
>one of them, but here is what I see.
>
>---
>Steve Fairbairn@stevefnec /cygdrive/d
>$ cat path_from_normal 
>/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/cygdrive/d/v80003/data/work/use
>rbin:/cygdrive/d/v80003/bin:/cygdrive/c/Program
>Files/j2sdk1.4.2_01/bin:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cy
>gdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/Program Files/Microsoft Visual
>Studio/VC98/Bin:/usr/bin
>---
>
>---
>Steve Fairbairn@stevefnec /cygdrive/d
>$ cat path_from_setup 
>/usr/bin:/usr/bin:/usr/bin:/usr/bin:?D-w@3"
>---

I'd be more interested in "cygcheck cygpath" output in the two different cases.
That would tell us which DLLs were being loaded.

cgf

--
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/

Re: cygpath hangings

[Brian Ford]

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\msvcrt.dll
    D:\WINNT\System32\KERNEL32.dll
      D:\WINNT\System32\ntdll.dll
  D:\WINNT\System32\SHELL32.DLL
    D:\WINNT\System32\GDI32.dll
      D:\WINNT\System32\USER32.dll
        D:\WINNT\System32\ADVAPI32.dll
          D:\WINNT\System32\RPCRT4.dll
    D:\WINNT\System32\SHLWAPI.dll
    D:\WINNT\System32\COMCTL32.dll

in bash and:

G:/cygwin/home/ford/cyghan.exe
  D:\WINNT\System32\msvcrt.dll
    D:\WINNT\System32\KERNEL32.dll
      D:\WINNT\System32\ntdll.dll
  D:\WINNT\System32\SHELL32.DLL
    D:\WINNT\System32\GDI32.dll
      D:\WINNT\System32\USER32.dll
        D:\WINNT\System32\ADVAPI32.dll
          D:\WINNT\System32\RPCRT4.dll
    D:\WINNT\System32\SHLWAPI.dll
    D:\WINNT\System32\COMCTL32.dll

from setup.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

--
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/

Re: cygpath hangings

[Christopher Faylor]

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
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: cygpath hangings

[Steve Fairbairn]

[-- Attachment #1: Type: text/plain, Size: 3118 bytes --]



> -----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 they are as well because of the 
> contents of
> one of them, but here is what I see.
> 
> ---
> Steve Fairbairn@stevefnec /cygdrive/d
> $ cat path_from_normal 
> /usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/cygdrive/d/v80003
> /data/work/use
> rbin:/cygdrive/d/v80003/bin:/cygdrive/c/Program
> Files/j2sdk1.4.2_01/bin:/cygdrive/c/WINDOWS/system32:/cygdrive
> /c/WINDOWS:/cy
> gdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/Program 
> Files/Microsoft Visual
> Studio/VC98/Bin:/usr/bin
> ---
> 
> ---
> Steve Fairbairn@stevefnec /cygdrive/d
> $ cat path_from_setup 
> /usr/bin:/usr/bin:/usr/bin:/usr/bin:ÓD-w@3"
> ---
> 

This is slightly false information.  The above run from setup was launched
using....   

Steve Fairbairn@stevefnec ~/obj
$ cygstart -- W:/Public/Installs/Installs/Cygwin/setup-2.415.exe --no-md5

When instead I double click on 'setup-2.415.exe' I end up with a path very
close to my normal bash one.

---
Steve Fairbairn@stevefnec /cygdrive/d
$ cat path_from_setup 
/usr/bin:/usr/bin:/usr/bin:/usr/bin:/cygdrive/d/v80003/data/work/userbin:/cy
gdrive/d/v80003/bin:/cygdrive/c/Program
Files/j2sdk1.4.2_01/bin:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cy
gdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/Program Files/Microsoft Visual
Studio/VC98/Bin:/usr/bin
---

Maybe tryig to debug this issue by using cygstart is giving false leads?

Steve.

-- 
-- LONG DISCLAIMER --

******************************************************* 
This email has originated from Perwill plc (Registration No. 1906964) 
Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK 
Tel: +44 (0)1420 545000 
Fax: +44 (0)1420 545001 
www.perwill.com 
******************************************************* 
Privileged, confidential and/or copyright information may be contained 
in this email, and is only for the use of the intended addressee. 
To copy, forward, disclose or otherwise use it in any way if you are not 
the intended recipient or responsible for delivering to him/her is
prohibited.
If you receive this email by mistake, please advise the sender immediately, 
by using the reply facility in your email software.

We may monitor the content of emails sent and received via our network 
for the purposes of ensuring compliance with policies and procedures. 
This message is subject to and does not create or vary any contractual 
relationships between Perwill plc and the recipient. 
******************************************************* 
Any opinions expressed in the email are those of the sender and not 
necessarily of Perwill plc.
******************************************************* 
This email has been scanned for known viruses using 
McAfee WebShield 4.5 MR1a 
******************************************************* 


  


[-- Attachment #2: path_from_setup --]
[-- Type: application/octet-stream, Size: 294 bytes --]

/usr/bin:/usr/bin:/usr/bin:/usr/bin:/cygdrive/d/v80003/data/work/userbin:/cygdrive/d/v80003/bin:/cygdrive/c/Program Files/j2sdk1.4.2_01/bin:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/Program Files/Microsoft Visual Studio/VC98/Bin:/usr/bin


[-- Attachment #3: Type: text/plain, Size: 218 bytes --]

--
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/