Re: Process does not respond to signals on read() of win32 handle

2002-11-06 Thread Christopher Faylor
On Wed, Nov 06, 2002 at 07:09:21PM -0500, [EMAIL PROTECTED] wrote: >thanks for the info. If I pass any "/dev/com" to >_cygwin_attach_handle_to_fd() it core dumps :-(. Not for me. You should actually be passing /dev/com1 in this case. I didn't pay close attention to your code but was taking your

Re: Process does not respond to signals on read() of win32 handle

2002-11-06 Thread Christopher Faylor
On Wed, Nov 06, 2002 at 07:30:42PM -0500, Harig, Mark A. wrote: >(Hmm. What is this 'redback' you speak of? :) I assume that this was his attempt to circumvent my Reply-To. He did eventually manage to send me private email on the subject. Isn't that special? cgf -- Unsubscribe info: http:

RE: Process does not respond to signals on read() of win32 handle

2002-11-06 Thread sanjayl
ot; or "/dev/com0"? > > (Hmm. What is this 'redback' you speak of? :) > > > -Original Message- > > From: [EMAIL PROTECTED] > [mailto:sanjayl@;mindspring.com] > > Sent: Wednesday, November 06, 2002 7:09 PM > > To: [EMAIL PROTECTED] >

RE: Process does not respond to signals on read() of win32 handle

2002-11-06 Thread Harig, Mark A.
[EMAIL PROTECTED] > Subject: Re: Process does not respond to signals on read() of win32 > handle > > > Christopher, > > thanks for the info. If I pass any "/dev/com" to > _cygwin_attach_handle_to_fd() it core dumps :-(. > > What is the significance of th

Re: Process does not respond to signals on read() of win32 handle

2002-11-06 Thread sanjayl
Christopher, thanks for the info. If I pass any "/dev/com" to _cygwin_attach_handle_to_fd() it core dumps :-(. What is the significance of the name param. Does it create a device node within the cygwin layer?? Can it be any path?? I am guessing from what you said, that if it is any random path,

Re: Process does not respond to signals on read() of win32 handle. (fwd)

2002-11-06 Thread Christopher Faylor
On Wed, Nov 06, 2002 at 04:22:18PM -0500, [EMAIL PROTECTED] wrote: >Hi Mark, > >I am running Cygwin on Windows 2000. Here is the output of uname -a > > > >CYGWIN_NT-5.0 REDBSUNJAY1 1.3.14(0.62/3/2) 2002-10-24 10:48 i686 unknown > >And here is a short program that can reproduce the bug. I just >Cre

FW: Process does not respond to signals on read() of win32 handle.

2002-11-06 Thread Harig, Mark A.
dspring.com] > Sent: Wednesday, November 06, 2002 4:20 PM > To: Harig, Mark A. > Subject: RE: Process does not respond to signals on read() of win32 > handle. > > > Hi Mark, > > I am running Cygwin on Windows 2000. Here is the output of uname -a > > CYGWIN_NT-5.0 R

RE: Process does not respond to signals on read() of win32 handle. (fwd)

2002-11-06 Thread sanjayl
gt; can and will help with this problem. > > > -Original Message- > > From: [EMAIL PROTECTED] > [mailto:sanjayl@;mindspring.com] > > Sent: Wednesday, November 06, 2002 1:51 PM > > To: [EMAIL PROTECTED] > > Subject: Process does not respond to signals > on read()

RE: Process does not respond to signals on read() of win32 handle.

2002-11-06 Thread Harig, Mark A.
iginal Message- > From: [EMAIL PROTECTED] [mailto:sanjayl@;mindspring.com] > Sent: Wednesday, November 06, 2002 1:51 PM > To: [EMAIL PROTECTED] > Subject: Process does not respond to signals on read() of > win32 handle. > > > I have a program that opens a Win2k driver usi

Process does not respond to signals on read() of win32 handle.

2002-11-06 Thread sanjayl
I have a program that opens a Win2k driver using CreateFile and then associates it with a file desciprtor using cygwin_attach_handle_to_fd(). I then do a read() on the descriptor. At this point the program stops responding to CTRL-Cs etc. until something is written to the device and the read() retu