Bug 340114 - Need better error message when gdb fails to connect to gdbserver
Summary: Need better error message when gdb fails to connect to gdbserver
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf-gdb (show other bugs)
Version: 8.0   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-16 02:49 EDT by Ang Chin Huat CLA
Modified: 2020-09-04 15:20 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ang Chin Huat CLA 2011-03-16 02:49:46 EDT 
Build Identifier: M20100909-0800

Try to debug any C/C++ application via gdbserver, intentionally let it fail by not starting gdbserver, observed the error message:

Error in final launch sequence
Failed to execute MI command:
-target-select extended-remote localhost:10000
Error message from debugger back end:
localhost:10000: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
localhost:10000: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. 


The error message should really be something more human-readible, e.g. unable to connect to remote target.

Reproducible: Always

Steps to Reproduce:
1. Create hello world project
2. Create new attach to application launch configuration, enable DSF.
3. In connections tab, use default settings, and do not start gdbserver.