From: Phil Muldoon <pmuldoon@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [python][patch] Add GDB Parameters functionality
Date: Tue, 27 Apr 2010 20:05:00 -0000 [thread overview]
Message-ID: <4BD7438F.8030508@redhat.com> (raw)
In-Reply-To: <83r5m0y9fp.fsf@gnu.org>
On 04/27/2010 08:36 PM, Eli Zaretskii wrote:
>>> I asked to say something about this translation, or provide an
>>> example.
>>
>> I'm just not sure what to say other than GDB will translate and encode
>> any escape sequences in the string. In fact, 'encoded' will probably
>> just do here without the 'translated' verb - it seems redundant with
>> the new encoded text. I think that is clearer. How about that with a
>> cross-reference to encoding (pxref{Character Sets})?
>
> Can you give me a couple of examples of this "translation"? Then I
> could suggest some simple explanation.
The simplest example I can think of is escaping octal to print
characters. So take this super simple string parameter:
class TestStringParam (gdb.Parameter):
show_doc = "Show some string"
set_doc = "Set some string"
def __init__ (self, name):
super (TestStringParam, self).__init__ (name, gdb.COMMAND_DATA, gdb.PARAM_STRING)
self.value = "foo"
test_file_param = TestStringParam ('test-string-param')
Invoke it in GDB via the python command:
(gdb) python
>class TestStringParam (gdb.Parameter):
> show_doc = "Show some string"
> set_doc = "Set some string"
> def __init__ (self, name):
> super (TestStringParam, self).__init__ (name, gdb.COMMAND_DATA, gdb.PARAM_STRING)
> self.value = "foo"
>test_file_param = TestStringParam ('test-string-param')
>end
Now test it:
(gdb) set test-string-param plain old text
(gdb) show test-string-para
Some string is "plain old text".
(gdb) set test-string-param \107\157\157\144\040\104\141\171 sir!
(gdb) show test-string-para
Some string is "Good Day sir!".
Does that help?
Cheers,
Phil
next prev parent reply other threads:[~2010-04-27 20:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 13:19 Phil Muldoon
2010-04-26 17:56 ` Eli Zaretskii
2010-04-27 12:26 ` Phil Muldoon
2010-04-27 17:45 ` Eli Zaretskii
2010-04-27 19:25 ` Phil Muldoon
2010-04-27 19:36 ` Eli Zaretskii
2010-04-27 20:05 ` Phil Muldoon [this message]
2010-04-28 2:59 ` Eli Zaretskii
2010-04-28 6:28 ` Phil Muldoon
2010-04-28 9:18 ` Phil Muldoon
2010-04-28 17:15 ` Eli Zaretskii
2010-04-28 20:31 ` Phil Muldoon
2010-04-29 3:06 ` Eli Zaretskii
2010-04-29 16:13 ` Phil Muldoon
2010-04-26 21:45 ` Tom Tromey
2010-04-26 21:52 ` Phil Muldoon
2010-04-27 3:09 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BD7438F.8030508@redhat.com \
--to=pmuldoon@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox