public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: bernard.haible@gmx.de
To: insight-gnats@sources.redhat.com
Subject: insight/318: Insight hangs when opening "Target Settings" window
Date: Sat, 28 Jul 2007 14:53:00 -0000	[thread overview]
Message-ID: <20070728144403.1299.qmail@sourceware.org> (raw)


>Number:         318
>Category:       insight
>Synopsis:       Insight hangs when opening "Target Settings" window
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jul 28 14:53:01 UTC 2007
>Closed-Date:
>Last-Modified:
>Originator:     Bernard Haible
>Release:        6.6
>Organization:
>Environment:
Windows XP Prof. / Cygwin / ASUS P5B-E
>Description:
Insight hangs when opening the "Target Settings" window.
>How-To-Repeat:

>Fix:
It seems that the problem is located the function itcl::body TargetSelection::port_list in file targetselection.itb. My PC has only one COM port. When searching for COM port 2 to 4, Insight hangs. 

I changed the search loop as follows, allowing quitting the loop after 1 port instead of 4 in the original code. With that change, it runs fine.

  for {set i 1} {!$quit} {incr i} {
    if {[catch { set fd [::open COM$i: RDWR] } msg]} {
      # Failed.  Find out why.
      if {[string first "permission denied" $msg] != -1} {
	# Port is there, but busy right now. That's OK.
	lappend plist /dev/com$i
      } elseif {$i > 1} {
	# if we've scanned the first 1 ports, then quit when we find no more 
	set quit 1
      }
    } else {
      # We got it.  Now close it and add to list.
      close $fd
      lappend plist /dev/com$i
    }
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2007-07-28 14:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070728144403.1299.qmail@sourceware.org \
    --to=bernard.haible@gmx.de \
    --cc=insight-gnats@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).