memory corruption when serial input overflows

I have run into a problem with the serial input (e.g. "COM1"). This is on WinXp Pro and cygwin 1.3.22. In the archives there are some references to this (or a similar?) issue. I got the idea that it is known that there are issues ... but nobody is working on them at this time. Here is a testcase

Re: Omniorb 4.0...

I have done it. It is feasible. Some work with the Makefiles though. In general, you have to add cygwin to omniORB's list of supported platforms, so that the configure script can auto-configure it correctly for you. Duncan Grisby (omniORB's CGF) has my patches and they might eventually make it

where can I get info on commercial version of cygwin

cygwin1.dll as part of that. I am happy to supply the cygwin source-tarballs also, but I can't supply the proprietary code that makes up the rest of the app. Any comment is highly appreciated. Thanks, ;Henning -- H. Henning Schmidt email: [EMAIL PROTECTED] -- Unsubscribe info: http://cygwi

RE: qt3 on cygwin

more appropriate. If you are talking about Qt/Win (commercial only), then you need to use the mingw gcc (not cygwin). ;Henning -- H. Henning Schmidt email: [EMAIL PROTECTED] phone: +49 (0) 6155 / 899 283 fax: +49 (0) 6155 / 899 284 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-s

RE: Serial Port?

://sources.redhat.com/ml/cygwin/2003-03/msg01529.html ;Henning -- _ H. Henning Schmidt LYNX Technik AG, Bickenbach, Germany email: [EMAIL PROTECTED] phone 1:+49 (0) 6150 / 18 17 - 20 phone 2:+49 (0) 6155 / 899 285 fax: +49 (0) 6155 / 899 284 The information in

pthread support ... broken in the past .. fixed now?

I am porting the omniORB CORBA-framework to cygwin. It makes heavy use of pthreads, I do not see a way to work around that ... so I need pthreads working in cygwin. I have found a number of messages in the the mailing-list archives referring to some major problems with pthreads under cygwin. Thes

RE: tcflush hang problem

I am pretty certain the the problem which is discussed in this thread has already been reported in http://sources.redhat.com/ml/cygwin/2003-03/msg01529.html There is obviously an input buffer, which overflows if you keep an open filedesc. on a serial port and let some external system generate in

cygwin source-patch fixing deadlock while writing to serial port

for me. I thought I'd share that with you. ;Henning -- H. Henning Schmidt email: [EMAIL PROTECTED] phone: +49 (0) 6155 / 899 283 fax: +49 (0) 6155 / 899 284 *** cygwin-1.5.5-1/winsup/cygwin/fhandler_serial.cc Sat Jun 21 02:12:35 2003 --- cygwin-1.5.5-1.corrected/winsup/c

Re: cygwin source-patch fixing deadlock while writing to serial port

> On Mon, Jan 19, 2004 at 10:08:39PM +0100, H. Henning Schmidt wrote: > >I found a potential deadlock while writing to a serial port (e.g. > >/dev/com1) that has been opened as O_RDWR. The deadlock occurs from time > >to time (not sure about exact conditions) when I write t

Re: cygwin source-patch fixing deadlock while writing to serial port

> > > > On Mon, Jan 19, 2004 at 10:08:39PM +0100, H. Henning Schmidt wrote: > > > > >I found a potential deadlock while writing to a serial port (e.g. > > > > >/dev/com1) that has been opened as O_RDWR. The deadlock occurs from time > > > > &

"test -c com1" hangs on some WinXP systems

er do "if test -c /dev/ttyS0" if possible, so that it's similar across all platforms we support. -- H. Henning Schmidt email: [EMAIL PROTECTED] phone: +49 (0) 6155 / 899 283 fax: +49 (0) 6155 / 899 284 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple

RE: gcc - static pointer initialization problem

This is pretty OT for this list. It's a plain "C" language issue. You are creating two instances of type , all named . One is instanciated and initialized as you expect in static_function_ptr_def.c. But this instance is , so it cannot be used from another module (i.e. from static_function_ptr.

is there a (cygwin?) method delivering the current version of windows?

eciated. Thanks, ;Henning -- H. Henning Schmidt email: [EMAIL PROTECTED] phone: +49 (0) 6155 / 899 283 fax: +49 (0) 6155 / 899 284 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http:/

Re: 1.5.10: problems relocating structures with function pointers

> I have discovered what may be a bug in the linker/relocater in cygwin > (or, more likely, I am doing something stupid again). > > When I use a structure containing function pointers, and this > structure is placed in an archive, then the function pointer becomes > NULL. As an example, compile t

verify login info on Windows

lot. ;Henning -- H. Henning Schmidt email: [EMAIL PROTECTED] phone: +49 (0) 6155 / 899 283 fax: +49 (0) 6155 / 899 284 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html

Re: verify login info on Windows

Igor Pechtchanski wrote: On Mon, 18 Jul 2005, H. Henning Schmidt wrote: I am developing a server application that accepts logins from a client over a proprietary protocol. I want to let clients login (username/password) before allowing anything else. I want to let them use username

RE: Serial Port Problems

after a timeout by configuring the appropriate members of the struct termios -member . Read http://www.easysw.com/~mike/serial/serial.html for details. ;Henning -- H. Henning Schmidt email: [EMAIL PROTECTED] phone: +49 (0) 6155 / 899 283 fax: +49 (0) 6155 / 899 284 -- Unsubscribe info