| Summary: | Debugger-specific action enabled while not debugging | ||
|---|---|---|---|
| Product: | [Developer tools] kdevplatform | Reporter: | Nicolás Alvarez <nalvarez> |
| Component: | debugger | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | aleixpol, niko.sams, piotr.mierzwinski, vlas.puhov |
| Priority: | NOR | ||
| Version: | git master | ||
| Target Milestone: | 1.3.0 | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
Nicolás Alvarez
2013-01-31 04:16:23 UTC
this action basically executes a "jump" command. Actually I've never used it, maybe we could even remove it? Personally I wouldn't miss it. It doesn't look like a safe action to run, unless you're debugging assembler code and you're completely sure you won't screw things up by skipping instructions. This patch solves it: 5647403baf36dc541ee5afead0017eb3b69006a6
Don't forget to delete/modify config file in $HOME dir, this'll do it:
find ~/ -name kdevdebuggershellui.rc -exec rm -f {} \;
Is it fixed then? Mark as fixed? Can we maybe make a fix so that our users don't have to nuke their configuration files? I think it's impossible ( is it? ), because kdevdebuggershellui.rc configuration file was designed for toolbar/menu editing, what if someone has modified it, or wants it to be the way it was? It won't be the right thing just to replace it. Maybe we should use global config only??
By the way, actually THIS patch fixex it:
9e0c2e15c10bb5437b3fe11b2bf59db9b66ccce4
The previous just adds jumpTo functionality to DisassembleWidget.
Actually it's not fixed. Please note that "Debug" view (application output) is still visible (for me on bottom of main window) in "Code" context. If you are talking about views that appear whenever you run/debug/build app, I don't think it's a problem, take a look at qtcreator, these views are visible in debug, edit... modes too. |