Bug 384412 - gdbconfig - not possible to add attributes to debugger shell script
Summary: gdbconfig - not possible to add attributes to debugger shell script
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: CPP Debugger (show other bugs)
Version: 5.1.2
Platform: Appimage Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-06 08:29 UTC by Manfred Eckschlager
Modified: 2022-12-10 05:14 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Manfred Eckschlager 2017-09-06 08:29:50 UTC
It seems to me that the problem lies in Config::DebuggerShellEntry which is of type QURL and therefore seems no to be able to receive more than one file entry. (no --arguments). If arguments are given here, nothing is started.

The tooltip states:
If you want gdb to be executed by a special shell script, which for example properly sets the library path, insert it here e.g.: /path/to/script.sh --scriptArguments</p><p>Note: your script'll be invoked like this: /path/to/script.sh --scriptArguments debugger --debuggerArguments.

The workaround at the moment is to pass all arguments in the field "debugger executable".

It seems that someone stopped in the middle of the job of refactoring those two fileds to the new format /path/to/script.sh --scriptArguments debugger --debuggerArguments :)
Comment 1 Kevin Funk 2017-09-06 08:53:39 UTC
@Manfred: Interested in helping out fixing this in the KDevelop source? Helping hands with the debugger component are *always* needed.

Building KDevelop is fairly easy these days, you'll find all instructions & communication channels here:
  https://www.kdevelop.org/contribute-kdevelop
Comment 2 Justin Zobel 2022-11-10 08:52:08 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-11-25 05:17:23 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2022-12-10 05:14:32 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!