This is the mail archive of the
insight-prs@sourceware.cygnus.com
mailing list for the Insight project.
insight/12: target remote COMx often does not work
- To: insight-gnats AT sourceware.cygnus dot com
- Subject: insight/12: target remote COMx often does not work
- From: till AT dasburo dot com
- Date: 17 Sep 1999 19:11:53 -0000
- Reply-To: till AT dasburo dot com
- Resent-Cc: insight-prs AT sourceware.cygnus dot com,
- Resent-Reply-To: gnats-admin@sourceware.cygnus.com, till@dasburo.com
- Resent-To: nobody AT sourceware.cygnus dot com
>Number: 12
>Category: insight
>Synopsis: target remote COMx often does not work
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Sep 17 12:13:01 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator: till@dasburo.com
>Release: insight-19990727
>Organization:
>Environment:
m68k-coff cross on Windows NT SP 4, Windows 95
>Description:
serial communication hangs. Program is only interruptable
if target sends a lot of output.
cat /dev/com2 works (with wrong baudrate)
>How-To-Repeat:
1) Start target, let it run into breakpoint. Start Debugger
with options -nw -b 38400 xxx.coff. enter target remote COM2.
-> Message:
1001 (0) fhandler_serial::tcsetattr:CommTimeout failed
set_tty_state failed: Bad file number
-> hangs forever
set remotetimeout or set watchdog does not help
2) Start debugger without -nw option.
select target settings.
connect to target.
-> no message, hangs forever
>Fix:
unfortunately none
>Release-Note:
>Audit-Trail:
>Unformatted: