Detect GDB problems already in launch config #178
Labels
Comments
|
2018-12 was released, this should work now ;) Thanks! |
|
@anb0s do you confirm this is fixed and we can close it? |
Boereck
added a commit
to Boereck/corrosion
that referenced
this issue
Nov 22, 2019
…metic changes Now the Rust debug launch config checks if the specified GDB is valid. This is done in a blocking fashion, tests show that this does not block the UI for an unreasonable time. Making the check non-blocking would also make the code much more complicated, since the launcher framework does not seem to be fit for such things. Also some cosmetic changes were done to the debug launch config. The "Main" tab now starts with a capital letter, as all other tabs. It also has an icon now.
Boereck
added a commit
to Boereck/corrosion
that referenced
this issue
Nov 22, 2019
…metic changes Now the Rust debug launch config checks if the specified GDB is valid. This is done in a blocking fashion, tests show that this does not block the UI for an unreasonable time. Making the check non-blocking would also make the code much more complicated, since the launcher framework does not seem to be fit for such things. Also some cosmetic changes were done to the debug launch config. The "Main" tab now starts with a capital letter, as all other tabs. It also has an icon now. Signed-off-by: Max Bureck <[email protected]>
Boereck
added a commit
to Boereck/corrosion
that referenced
this issue
Nov 22, 2019
…metic changes Now the Rust debug launch config checks if the specified GDB is valid. This is done in a blocking fashion, tests show that this does not block the UI for an unreasonable time. Making the check non-blocking would also make the code much more complicated, since the launcher framework does not seem to be fit for such things. Also some cosmetic changes were done to the debug launch config. The "Main" tab now starts with a capital letter, as all other tabs. It also has an icon now. Signed-off-by: Max Bureck <[email protected]>
Boereck
added a commit
that referenced
this issue
Nov 22, 2019
Now the Rust debug launch config checks if the specified GDB is valid. This is done in a blocking fashion, tests show that this does not block the UI for an unreasonable time. Making the check non-blocking would also make the code much more complicated, since the launcher framework does not seem to be fit for such things. Also some cosmetic changes were done to the debug launch config. The "Main" tab now starts with a capital letter, as all other tabs. It also has an icon now. Signed-off-by: Max Bureck <[email protected]>
Boereck
added a commit
to Boereck/corrosion
that referenced
this issue
Dec 8, 2019
…metic changes Now the Rust debug launch config checks if the specified GDB is valid. This is done in a blocking fashion, tests show that this does not block the UI for an unreasonable time. Making the check non-blocking would also make the code much more complicated, since the launcher framework does not seem to be fit for such things. Also some cosmetic changes were done to the debug launch config. The "Main" tab now starts with a capital letter, as all other tabs. It also has an icon now. Signed-off-by: Max Bureck <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since in some cases, like #149, it would be beneficial if the GDB version would be detected already when the GDB location is entered. If errors occur, they can then be presented to the user already in the launch config to give users early and detailed feedback. The necessary functionality in CDT will be added with SimRel 2018-12 M3 (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=541520).
The text was updated successfully, but these errors were encountered: