Bug 148557 - No debugger configuration available for C - Cross develonpmet
Summary: No debugger configuration available for C - Cross develonpmet
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: 3.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-25 04:47 EDT by Nostalghia CLA
Modified: 2020-09-04 15:20 EDT (History)
0 users

See Also:

Attachments
screen shot, showing the error. (88.60 KB, image/png)
2006-06-25 04:51 EDT, Nostalghia CLA 		no flags Details
View All 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 Nostalghia CLA 2006-06-25 04:47:02 EDT 
I am using Eclipse Version: 3.2.0 (Build id: I20060602-1317)
with CDT Version: 3.1.0.200605290500 (Build id: 200605290500). Cross compiling C-Code for Atmel ATmega processors works fine with the gcc – avr tool chain. I can compile and link the C – sources from inside Eclipse.

But it is not possible to use avr - gdb. It's not remote debugging. Instead of then embedded controller I am using a locally running software emulator. (simulavr).

In the “Create, manage and run configurations ” in tab “Debugger” I am setting the field Debugger to “gdb Debuger”, field GDB Debugger to “/opt/cdk4avr/bin/avr-gdb” and field GDB command file to “/home/strom/workspace_callisto/HAL-ct_bot-atmega32/simulavr.gdbinit”. Protocol is default.
And got the error message “The CPU is not supported by selected debugger.”

May be this bug is related to Bug#: 110897.

Same strategy worked fine for debugging ATmega code with Eclipse 3.1.0 and CDT 3.0.1.
Comment 1 Nostalghia CLA 2006-06-25 04:51:51 EDT 
Created attachment 45261 [details]
screen shot, showing the error.