[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 144501] changing debug arguments to empty(or something wrong)
From:       yzhh <yezonghui () gmail ! com>
Date:       2007-04-22 8:17:35
Message-ID: 20070422081735.9305.qmail () ktown ! kde ! org
[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         




------- Additional Comments From yezonghui gmail com  2007-04-22 10:17 -------
Now I've made the problem more clear: it's a matter of restarting the gdb front/back \
end.

That is, if I go a debugging run with 'good' debug arguments, and follow with another \
run with modified (bad) debug arguments, without manually stopping gdb front/back \
end, the gdb session is reused. However, 'set args' command is only sent to gdb in \
the first run. This way changes to debug arguments are not made available to gdb.  \
Stopping gdb front/back end will force a 'set args' command in the next debugging \
run.

I have a copy of the gdb session illustrating the above. See the attachment. The \
program is as simple as this ( created from CMake C++ hello world template, modified \
CMAKE_BUILD_TYPE in CMakeCache.txt to enable debugging):

#include <stdio.h>
#include <stdlib.h>

int main(int argc, char *argv[])
{
	char hello[20];
	scanf("%s", hello);
	printf(hello);

	return EXIT_SUCCESS;
}

Although stopping gdb between debugging runs is only one click and reasonable, do \
'set args' before each debugging run is not a big deal either (and also reasonable). \
It'll make life easier for non-kdevelop-professionals like me.


[prev in list] [next in list] [prev in thread] [next in thread]