| Summary: | Unable to use GDB plugin | ||
|---|---|---|---|
| Product: | [Applications] kate | Reporter: | caulier.gilles |
| Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | justin.zobel, kare.sars |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
caulier.gilles
2016-12-30 10:13:19 UTC
Add "set unwindonsignal on" to Advanced Settings/Custom Init Commands permit to start debuging session after to use Debug/Continue. But this is obscur. There is no documentation somewhere explaining the basing, no tooltip, etc.... Nobody will investigate in settings to try hidden settings. This is not user friendly as expected. Please improve this plugin. Thanks in advance Thanks for the report. The "p setvbuf(stdout, 0, 1, 1024)" command is used to set the stdout of the debugged application to unbuffered mode. This is a workaround for not using a proper tty... My suspicion is that the unwinding of the stack of setvbuf() and continuing from main just happens to work even if we get a segfault in setvbuf(). The proper solution here would be to not use the tty-workaround hack... Can someone please test this to confirm if this is still an issue in current kate, thanks. 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! 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! |