public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: craig@triscend.com
To: insight-gnats@sources.redhat.com
Subject: insight/149: Connection to remote (serial) target fails if target selection dialog is not displayed.
Date: Tue, 07 May 2002 11:43:00 -0000	[thread overview]
Message-ID: <20020507183535.6986.qmail@sources.redhat.com> (raw)


>Number:         149
>Category:       insight
>Synopsis:       Connection to remote (serial) target fails if target selection dialog is not displayed.
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue May 07 11:43:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     craig@triscend.com
>Release:        unknown-1.0
>Organization:
>Environment:
Windows 2000/Cygwin
>Description:
There has been a change in Insight where the target selection window is only displayed if Target Settings is selected by the user or no target is set.
This causes problems for serial remote targets like Cygmon, because if the target selection window is not displayed, the the remote serial baudrate is not set.
>How-To-Repeat:

>Fix:
Sorry no patch file, but...
In interface.tcl, add a line that calls set_baud just before the remote connection is made, see below...

    debug "CONNECTING TO TARGET: $gdb_target_cmd"

    #
    # If the target selection windows was not displayed because
    # the target was already configured, the baud rate will not
    # be set correctly, so call set_baud.
    #
    set_baud
    set err [catch {gdb_immediate "target $gdb_target_cmd"} msg ]
    $srcWin set_status
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2002-05-07 18:43 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=20020507183535.6986.qmail@sources.redhat.com \
    --to=craig@triscend.com \
    --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).