Hi All, User defined commands gets messed up if a definition has a name
starting with "ws" and called from another definition. Is it a known defect?
Any workarounds? bash-3.2$ cat test.gdb
define wsbaz
printf "wsbaz\n"
enddefine foo
wsbaz
enddefine bar
printf "bar\n"
end b
A small correction in the test.gdb file which I pasted earlier. This is the
correct one... bash-3.2$ cat test.gdb
define wsfoo
printf "wsfoo\n"
end
define foo
wsfoo
end
define bar
printf "bar\n"
end
From: mohanasundaram.subscr...@outlook.com
To: bug-gdb@gnu.org
Subject: Pr
Another info...this works in gdb 6.5 but not working in 7.2 and 7.5.1 which I
tried...
From: mohanasundaram.subscr...@outlook.com
To: bug-gdb@gnu.org
Subject: RE: Problem with user defined commands
Date: Wed, 30 Jan 2013 16:22:02 +0530
A small correction in the test.gdb file which I pasted ea
We figured that the problematic code was this
/* Check for while, if, break, continue, etc and build a new
command line structure for them. */
if ((p_end - p >= 14 && !strncmp (p, "while-stepping", 14))
|| (p_end - p >= 8 && !strncmp (p, "stepping", 8))
||
Forgot to mention the file /gdb/cli/cli-script.c
From: mohanasundaram.subscr...@outlook.com
To: bug-gdb@gnu.org
Subject: RE: Problem with user defined commands
Date: Wed, 30 Jan 2013 17:35:40 +0530
We figured that the problematic code was this
/* Check for while, if, break, continue, et
