Eclipse Community Forums: C / C++ IDE (CDT) » Launch Bar: No launch configuration is found for the given launch descriptor and target

Home » Language IDEs » C / C++ IDE (CDT) » Launch Bar: No launch configuration is found for the given launch descriptor and target(GDB Hardware Debugging launch configuration has no launch target entry in the Launch Bar causing malfunction.)

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

Launch Bar: No launch configuration is found for the given launch descriptor and target [message #1863555]

Fri, 09 February 2024 09:21

Rudolf Reinsberger

Messages: 1
Registered: March 2019

Junior Member

I have created a custom launch configuration for some custom hardware debugging using gdb infrastructure. The launch delegate for this launch configuration extends the GDBJtagDSFLaunchConfigurationDelegate. So far this all worked and works well using the standard Run menu commands. Now a user has an Eclipse with the Launch Bar component installed and the custom launch configuration does not work there. That means, neither the Launch Bar Debug launch button nor the Stop button nor the gear wheels in the configuration and target drop downs work when a custom launch configuration is selected. In fact the target drop down indicates the "null target" (by showing: ---) from what I understood.

Trying the Launch Bar with a generic "GDB Hardware Debugging" launch configuration shows the same behavior.

Now, the source code comment for the GDBJtagDSFLaunchConfigurationDelegate reads that " This delegate only supports the org.eclipse.cdt.debug.gdbjtag.launchConfigurationType launch configuration types." I noticed that launches using other delegates and configuration types don't show this behavior (e.g. a "C/C++ Application" launch on the host indicates "Local" in the launch target drop down and works as expected). Another aspect I noticed is that for some configurations new launch targets can be specified via the gear wheel in the launch target drop down. However, the settings made there don't seem to have any influence on the respective launch, even id they are completely randomized.

My current ambition is to find a quick solution, a shortcut even, to make the custom launch work with the Launch Bar. Does anybody know what I am missing here, respectively why a custom launch configuration which showed no problems so far won't work with the Launch Bar component OOTB ?

Report message to a moderator

Re: Launch Bar: No launch configuration is found for the given launch descriptor and target [message #1867758 is a reply to message #1863555]

Sat, 06 July 2024 07:02

Smith Jones

Messages: 1
Registered: July 2024

Junior Member

The issue you're encountering with your custom launch configuration not functioning properly with the Launch Bar component in Eclipse seems to be related to the specific delegate (GDBJtagDSFLaunchConfigurationDelegate) that your configuration extends. Here's a breakdown of the situation and a potential approach to resolve it:

Understanding the Problem:
Delegate Limitations: The GDBJtagDSFLaunchConfigurationDelegate is designed specifically for launch configurations of type org.eclipse.cdt.debug.gdbjtag.launchConfigurationType. This delegate may have specific expectations or behaviors tailored to this type of launch configuration.

Launch Bar Compatibility: The Launch Bar in Eclipse, which includes the Debug launch button, Stop button, and configuration/target dropdowns, relies on standard behaviors and interfaces defined for launch configurations. If a custom launch configuration extends a delegate that doesn't fully adhere to these standards or isn't fully compatible, it may not work as expected with the Launch Bar.

Behavior Differences: Other standard launch configurations (like "C/C++ Application") work correctly with the Launch Bar, indicating that the issue isn't with the Launch Bar itself but with how your custom configuration interacts with it.

Possible Solutions:
To address this issue and enable your custom launch configuration to work with the Launch Bar, consider the following steps:

Review Delegate Implementation:

Ensure that the GDBJtagDSFLaunchConfigurationDelegate implementation is correctly handling all necessary interfaces and behaviors expected by Eclipse launch mechanisms, including the Launch Bar. Check for any specific methods or behaviors that might need to be implemented or adjusted.
Compatibility Check:

Compare the behavior and implementation of the GDBJtagDSFLaunchConfigurationDelegate with other delegates that work correctly with the Launch Bar. Look for any discrepancies or missing implementations that might be causing the issue.
Consult Documentation and Forums:

Review the Eclipse CDT documentation and community forums for any specific guidance or known issues related to custom launch configurations and their compatibility with the Launch Bar. Sometimes, there are specific configurations or adjustments recommended for custom delegates to ensure compatibility.
Debugging and Logging:

Use Eclipse's debugging capabilities and logging features to trace the execution path of your custom launch configuration. This can help identify where the behavior diverges from expected norms, especially when compared to standard configurations.
Consider Alternative Approaches:

If adjusting the existing delegate proves challenging, consider creating a new custom delegate that adheres more closely to standard Eclipse launch configuration behaviors.

Report message to a moderator

Previous Topic:	build or other task realy slow
Next Topic:	Eclipse IDE for Embedded and Device Support

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Mon Dec 30 16:55:47 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter