Eclipse Community Forums: C / C++ IDE (CDT) » Eclipse Juno CDT Error in final launch sequence

Help

Home

Home » Language IDEs » C / C++ IDE (CDT) » Eclipse Juno CDT Error in final launch sequence

Show: Today's Messages :: Show Polls :: Message Navigator

Eclipse Juno CDT Error in final launch sequence [message #1019494]

Fri, 15 March 2013 20:38

Edzard Egberts

Messages: 57
Registered: July 2009

Member

I'm using CentOS 6.4 and out of the Repository I installed an Eclipse
Helios. It works and debugs C++-code.

@work I'm used to use Juno, so I installed Eclipse Juno to a Folder and
executing it works, but there is a problem. The project builds, but
Debugger doesn't start:
<
Error in final launch sequence
Failed to execute MI command:
maintenance set python print-stack off
Error message from debugger back end:
Undefined maintenance set python command: "print-stack off". Try "help
maintenance set python".
Undefined maintenance set python command: "print-stack off". Try "help
maintenance set python".
>

This doesn't seem to be a problem of access, because also a "sudo
eclipse" doesn't resolve the problem.

I just installed Eclipse Juno under Windows-XP and it works at once,
also at Fedora 14, so there must be a special difference to CentOs. What
could it be?

Report message to a moderator

Re: Eclipse Juno CDT Error in final launch sequence [message #1019533 is a reply to message #1019494]

Fri, 15 March 2013 23:28

Marc Khouzam

Messages: 357
Registered: July 2009

Senior Member

You must have recently changed your GDB version. This problem has been reported on non-standard GDBs which have removed the command "maintenance set python" but have not followed the standard GDB versioning.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=402988

CDT will improve its solution to handle such cases better, but that will only be available in the next release (Kepler) due in June.

The only workaround is to change your GDB version to what worked before or to use the standard FSF GDB.

Marc

P.S. I don't believe Helios would work with such a version of GDB either...

Report message to a moderator

Re: Eclipse Juno CDT Error in final launch sequence [message #1019674 is a reply to message #1019533]

Sat, 16 March 2013 10:00

Edzard Egberts

Messages: 57
Registered: July 2009

Member

Marc Khouzam wrote:
> You must have recently changed your GDB version.

I switched from Fedora to CentOS-6.4, it provides "GNU gdb (GDB) Red Hat
Enterprise Linux (7.2-60.el6)".

> https://bugs.eclipse.org/bugs/show_bug.cgi?id=402988

Ups, the report names the same gdb-version.

> The only workaround is to change your GDB version to what worked before
> or to use the standard FSF GDB.

One of my debug configurations works, but I don't understand, how to
reproduce it:

The [Debug Configurations]->[C/C++ Application]->my_project works, when
on page [Debugger] there is a Debugger of "gdb/mi" and using "GDB
command set: Standard (Linux)", "Protocol: mi". This is a part of the
page completely different to the [Debug Configurations] that doesn't
work: There is a Debugger of "gdb" and the whole part of "command set/
protocol" is replaced by some (unchecked) checkboxes.

So there is a working workaround (it really works, I started
GUI-software after clean build), but how to set it up?

Report message to a moderator

Re: Eclipse Juno CDT Error in final launch sequence [message #1019738 is a reply to message #1019674]

Sat, 16 March 2013 14:24

Marc Khouzam

Messages: 357
Registered: July 2009

Senior Member

Ah yes, you can use CDT's older GDB integration. Thanks for mentioning it. That solution doesn't support any of the new features introduced by GDB, but it is still a good debugger solution.
Here how to choose it:

http://wiki.eclipse.org/CDT/User/FAQ#How_can_I_choose_another_debugger_integration_for_CDT.3F

Marc

Report message to a moderator

Re: Eclipse Juno CDT Error in final launch sequence [message #1019746 is a reply to message #1019738]

Sat, 16 March 2013 14:42

Edzard Egberts

Messages: 57
Registered: July 2009

Member

Marc Khouzam wrote:
> Ah yes, you can use CDT's older GDB integration. Thanks for mentioning
> it. That solution doesn't support any of the new features introduced by
> GDB, but it is still a good debugger solution.

Nice to meet a win win situation. ;o)

> Here how to choose it:
>
> http://wiki.eclipse.org/CDT/User/FAQ#How_can_I_choose_another_debugger_integration_for_CDT.3F

Thank you, that solves my problem. I will try to switch back, when there
is an update of gdb or eclipse.

Report message to a moderator

Previous Topic:	Installing boost with eclipse
Next Topic:	Support for developing WinCE application by using Eclipse IDE

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 22:58:27 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter