This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug python/18494] Python gdb.Command#complete is provided with wrong parameters
- From: "arma2ff0 at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sat, 06 Jun 2015 12:41:06 +0000
- Subject: [Bug python/18494] Python gdb.Command#complete is provided with wrong parameters
- Auto-submitted: auto-generated
- References: <bug-18494-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18494
--- Comment #2 from Armando <arma2ff0 at gmail dot com> ---
Hi Sergio.
thank you for your reply.
After reading your reply I got doubts about whether I remembered the behavior
of the previous version of GDB correctly. However I was pretty sure that the
variable "word" was containing the content I was expecting.
Luckily, I did not clean pacman's cache so I was able to down-grade gdb to
7.8.2 to test the behavior of that version. To me, it looks that this version's
behavior is in-line with what is described in the documentation.
Test:
$ gdb --version
GNU gdb (GDB) 7.8.2
[..]
$ gdb -x /tmp/test.py
(gdb) bug-test text: ''; word ''
text: ''; word ''
text: ''; word ''
(gdb) bug-test abc deftext: 'abc def'; word 'def'
text: 'abc def'; word 'def'
text: 'abc def'; word 'def'
text: 'abc def'; word 'def'
as the cursor is at the end of "def" while the rest of the argument is in text,
this looks like the correct behavior.
Do you agree?
Still, my expectations were clearly wrong, as I was expecting text to contain
the whole command, while word to contain the arguments. Anyway, I currently not
100% sure what the correct behavior should be, but clearly it changed between
7.8 and 7.9 :)
Thanks.
A.
--
You are receiving this mail because:
You are on the CC list for the bug.