This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: Serial port problems with cygwin1.dll 1.3.15 on Win98SE
- From: "lhall at pop dot ma dot ultranet dot com" <lhall at pop dot ma dot ultranet dot com>
- To: v-overbeek at cistron dot nl, cygwin at cygwin dot com
- Date: Wed, 13 Nov 2002 17:19:20 -0500
- Subject: RE: Serial port problems with cygwin1.dll 1.3.15 on Win98SE
- Reply-to: lhall at rfk dot com
If you can zero in on the snapshot where you notice this
behavior first occuring, that would be useful information.
Larry
Original Message:
-----------------
From: Ton van Overbeek v-overbeek@cistron.nl
Date: Wed, 13 Nov 2002 22:20:53 +0100
To: cygwin@cygwin.com
Subject: Serial port problems with cygwin1.dll 1.3.15 on Win98SE
When using a cross debugger (m68k-palmos-gdb) talking to a Palm device
via the serial port on W98SE my system completely hangs.
What I have been able to deduce is that it happens as soon as the Palm
sends a debug packet to the PC.
M68k-palmos-gdb opens the serial port, sets the baudrate to 57600 and puts
the port in raw mode.
You can still interrupt the program and do other things after this, provided
the Palm has not sent any data yet.
As soon as it sends data (e.g. when you start the program you want to debug)
the whole system hangs. Ctrl-Alt-Delete gives a blue screen etc.
I went back to older versions of cygwin1.dll and everything works fine up to
version 1.3.14. So something happened between 1.3.14 and 1.3.15.
I suspect some of the recent changes to fhandler-serial.cc.
Any hints on how to debug this? snapshots to try?
Output from cygcheck -s -r -v attached.
Ton van Overbeek
--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/