[kdevelop] [Bug 368292] Segfault when using gdb
https://bugs.kde.org/show_bug.cgi?id=368292 Sven Brauchchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #7 from Sven Brauch --- *** This bug has been marked as a duplicate of bug 368301 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368292] Segfault when using gdb
https://bugs.kde.org/show_bug.cgi?id=368292 Milian Wolffchanged: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368292] Segfault when using gdb
https://bugs.kde.org/show_bug.cgi?id=368292 --- Comment #6 from Sven Brauch--- 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. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368292] Segfault when using gdb
https://bugs.kde.org/show_bug.cgi?id=368292 --- Comment #5 from Gregor Mi--- 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. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368292] Segfault when using gdb
https://bugs.kde.org/show_bug.cgi?id=368292 Sven Brauchchanged: What|Removed |Added Status|CONFIRMED |UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368292] Segfault when using gdb
https://bugs.kde.org/show_bug.cgi?id=368292 --- Comment #4 from Sven Brauch--- Should have an icon there, do you have the icon border enabled? The icon is a bit strange. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368292] Segfault when using gdb
https://bugs.kde.org/show_bug.cgi?id=368292 --- Comment #3 from Gregor Mi--- 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? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368292] Segfault when using gdb
https://bugs.kde.org/show_bug.cgi?id=368292 --- Comment #2 from Sven Brauch--- Mh, can't reproduce. Anything special you did there ...? Can you be more explicit about the setup? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368292] Segfault when using gdb
https://bugs.kde.org/show_bug.cgi?id=368292 Sven Brauchchanged: What|Removed |Added Assignee|kdevelop-bugs-n...@kde.org |m...@svenbrauch.de -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368292] Segfault when using gdb
https://bugs.kde.org/show_bug.cgi?id=368292 Kevin Funkchanged: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Kevin Funk --- 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. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368292] Segfault when using gdb
https://bugs.kde.org/show_bug.cgi?id=368292 Kevin Funkchanged: What|Removed |Added CC||m...@svenbrauch.de -- You are receiving this mail because: You are watching all bug changes.