At 19:46 11/13/2002 -0500, Sergei Okhapkin wrote: >Could you run "strace -o tracefile m68k-palmos-gdb ....", do everything >you need to hang the system and send the tracefile (compressed!) to me? >The tracefile will be huge.... > and at 17:19 11/13/2002 -0500, Larry Hall wrote: >If you can zero in on the snapshot where you notice this >behavior first occuring, that would be useful information. >
Did both things. The last snapshot which still works is 20021103. The 20021106 snapshot and 1.3.15-2 have the problem. Attached the compressed strace output from a run with the 1.3.15-2 release dll. Command used is 'strace -o tracefile -S 1 -w m68k-palmos-gdb'. After start of gdb I typed 'target pilot com4' which should establish communication with the palm via COM4:. When the program was hanging I killed it via the Windows task manager. Windows task manager showed the 'm68k-palmos-gdb is not responding' message. Original message got rejected by spam filter (probably the strace logfile attachments). So for the archive here the message I sent to Sergey Okhapkin and Larry Hall -------------------------------------------------------------------- Looking at the strace output it seems to be hanging in fhandler_serial::raw_read. I also tried the 20021113 and 20021114 snapshots. Both have the problem. A second tracefile is attached from a run with the 20021114 snapshot. Hope you can make some sense out of it. Wild guess, something with rts/dtr ? Ton van Overbeek
trace-20021114.bz2
Description: Binary data
trace-1-3-15.bz2
Description: Binary data
-- 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/
