[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-bugs
Subject: [Bug 144501] New: changing debug arguments to empty(or something
From: yzhh <yezonghui () gmail ! com>
Date: 2007-04-21 16:29:40
Message-ID: 20070421182939.144501.yezonghui () gmail ! com
[Download RAW message or body]
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=144501
Summary: changing debug arguments to empty(or something wrong)
needs reopening project to take effect
Product: kdevelop
Version: 3.4.0
Platform: unspecified
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: kdevelop-bugs kdevelop org
ReportedBy: yezonghui gmail com
Version: 3.4.0 (using KDE KDE 3.5.5)
OS: Linux
I'm using kdevelop 3.4.0 under debian testing. A very similar bug was reported and \
solved for 3.0 (bug 59529). Seems it shows up again with subtle differences.
The problem is with debug arguments (which is now separated from run arguments, both \
provided in "run options" tag of Projects Options):
1. When it is set to something good (in my case "< input.txt", to redirect standard \
input to a text file), the debugging takes the arguments to run. But after this, \
changing it (debug arguments) to anything else (including empty string or invalid \
arguments, eg. "< file_not_exist.txt") would require reopening project or restarting \
kdevelop to make the change take effect.
2. The funny thing is that if the project is firstly loaded with invalid arguments \
and the debugger encountered errors (in my case bash complains about non-existent \
file), then changing debug arguments to something right will take effect immediately \
on the next debugging run (project not rebuilt - I assure).
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic