|
Re: Problem with CDT3.0: The CPU is not supported by selected debugger. [message #148489 is a reply to message #148170] |
Sat, 09 July 2005 06:06 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: azcoder.cox.net
I have the exact same problem.
Jerome Correnoz wrote:
> Hello,
>
> I've just downloaded Eclipse 3.1 and CDT 3.0 RC1, then I've added my
> plug-in for ST processor.
>
> When I try to launch a debug session for ST processor, I select the ST
> dedicated debugger but I have the following error message in the "Debug
> configuration" window:
> "The CPU is not supported by selected debugger."
>
> Note 1: It works fine with CDT 3.0 M6 and CDT 2.1.x releases.
> Note 2: If I select "Cygwin Debugger" I have no more the message but it is
> not the dedicated debugger.
>
> Is it a known regression bug ?
>
> Thanks
> Jerome
|
|
|
Re: Problem with CDT3.0: The CPU is not supported by selected debugger. [message #148497 is a reply to message #148489] |
Sat, 09 July 2005 06:12 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: azcoder.cox.net
Just to clarify - I get the smae error message in the build settings dialgo,
but I can still debug the application using gdb just fine.
R Cober wrote:
>
> I have the exact same problem.
>
>
>
> Jerome Correnoz wrote:
>
>> Hello,
>>
>> I've just downloaded Eclipse 3.1 and CDT 3.0 RC1, then I've added my
>> plug-in for ST processor.
>>
>> When I try to launch a debug session for ST processor, I select the ST
>> dedicated debugger but I have the following error message in the "Debug
>> configuration" window:
>> "The CPU is not supported by selected debugger."
>>
>> Note 1: It works fine with CDT 3.0 M6 and CDT 2.1.x releases.
>> Note 2: If I select "Cygwin Debugger" I have no more the message but it
>> is not the dedicated debugger.
>>
>> Is it a known regression bug ?
>>
>> Thanks
>> Jerome
|
|
|
Powered by
FUDForum. Page generated in 0.03545 seconds