This is the mail archive of the
insight-prs@sourceware.org
mailing list for the Insight project.
Re: insight/277: Error: Couldn't establish connection to remote target
- From: kseitz at sources dot redhat dot com
- To: insight-prs at sources dot redhat dot com, kseitz at sources dot redhat dot com, nobody at sources dot redhat dot com, raquelsacristan at yahoo dot es
- Date: 11 Nov 2005 17:34:19 -0000
- Subject: Re: insight/277: Error: Couldn't establish connection to remote target
- Reply-to: kseitz at sources dot redhat dot com, insight-prs at sources dot redhat dot com, kseitz at sources dot redhat dot com, nobody at sources dot redhat dot com, raquelsacristan at yahoo dot es, insight-gnats at sources dot redhat dot com
Synopsis: Error: Couldn't establish connection to remote target
Responsible-Changed-From-To: unassigned->kseitz
Responsible-Changed-By: kseitz
Responsible-Changed-When: Fri Nov 11 17:34:19 2005
Responsible-Changed-Why:
mine
State-Changed-From-To: open->analyzed
State-Changed-By: kseitz
State-Changed-When: Fri Nov 11 17:34:19 2005
State-Changed-Why:
This sounds like a gdb "problem". Your best bet is to communicate with the gdb folks, since they outnumber me by about 50. You'll get your problem resolved a whole lot faster.
Anyway, your problem seems to indicate that you are using the wrong com port configuration in Insight/gdb. Make sure that the baud rate is appropriate set and that the target is responding.
The best way to troubleshoot problems like this is to run command-line gdb and use "set debug remote 1", taking the results to the gdb list.
http://sourceware.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=insight&pr=277