Bug 76084

Summary: GDB Debugger not detected
Product: [Retired] Red Hat Developer Suite Reporter: Need Real Name <ahussain>
Component: eclipseAssignee: Tom Tromey <tromey>
Status: CLOSED CURRENTRELEASE QA Contact: Tom Tromey <tromey>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0CC: patrickm
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-10-16 18:00:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Need Real Name 2002-10-16 18:00:47 UTC
Description of Problem:
The Debugger tab in the Launch Configuration dialog box always has the error:
"[Debugger]: No debugger avalible" although the Debugger selection box shows
"GDB Debugger"

Version-Release number of selected component (if applicable):


How Reproducible:

Always in current rpm

Steps to Reproduce:
1. Create and build a C project
2. Go to Run->Debug
3. Choose the program to be executed in the C/C++ Applications box.
4. Go to the Debugger tab. GDB debugger is selected but there's still an error.


Additional Information:

The error message also has  spelling mistake. It should be "no debugger
AVAILABLE" (not avalible).

Comment 1 Tom Tromey 2002-10-17 18:04:26 UTC
I've checked in a fix for this.

The typo is already fixed in the public tree and will
show up with the next CDT import.

The other bug is in our local tree.  I'm working with
someone at QNX to get a different fix into the public
tree.

(It would make sense to add this particular bug to our
test plan.  That way we can be sure that future imports
don't cause a regression here.)