Summary: | Segfault when using gdb | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Gregor Mi <codestruct> |
Component: | general | Assignee: | Sven Brauch <mail> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | |
Priority: | NOR | ||
Version First Reported In: | 5.0.0 | ||
Target Milestone: | --- | ||
Platform: | Appimage | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Gregor Mi
2016-09-05 19:33:09 UTC
Note: this crash only happened when we had a non-empty environment set for the executable in the "Configure Launches..." dialog. Executable started fine with an empty env. Mh, can't reproduce. Anything special you did there ...? Can you be more explicit about the setup? I cannot reproduce the crash either. While reproducing a re-discovered a related bug: the debugger (gdb) halts at positions at the code where I used to have a break point but it still halts there. How are break points to be indicated nowadays? Toggle a break point highlights the current line slightly red. Are there no circles on the left bar anymore? Should have an icon there, do you have the icon border enabled? The icon is a bit strange. Oh yes, the icon border was disabled. The breakpoint icon is indeed strange. Related question: the toggle icon border has the default shortcut F6. Is this really needed to have a default shortcut? Because the F keys could better be used for debugging or building. That shortcut comes from kate and would need to be changed there. I don't think any of the F6-F* things needs a default shortcut, except maybe dynwrap. Having a shortcut for show line numbers does more harm than good, and we should just turn it on by default. *** This bug has been marked as a duplicate of bug 368301 *** |