From: Phil Muldoon <pmuldoon@redhat.com>
To: tromey@redhat.com
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [patch][python] Implement Python lazy strings (PR 10705)
Date: Mon, 11 Jan 2010 21:40:00 -0000 [thread overview]
Message-ID: <4B4B9ADD.9030200@redhat.com> (raw)
In-Reply-To: <4B4B9867.5080805@redhat.com>
On 01/11/2010 09:30 PM, Phil Muldoon wrote:
> On 01/11/2010 09:08 PM, Tom Tromey wrote:
>>>>>>> "Phil" == Phil Muldoon <pmuldoon@redhat.com> writes:
>>
>> Phil> Index: gdb/varobj.c
>> [...]
>> Phil> + if (is_lazy_string (output))
>> Phil> + thevalue = extract_lazy_string (output, &type,
>> Phil> + &len, &encoding);
>> Phil> + else
>> Phil> {
>> Phil> - char *s = PyString_AsString (py_str);
>> Phil> - len = PyString_Size (py_str);
>> Phil> - thevalue = xmemdup (s, len + 1, len + 1);
>> Phil> - Py_DECREF (py_str);
>> Phil> + PyObject *py_str
>> Phil> + = python_string_to_target_python_string (output);
>> Phil> + if (py_str)
>> Phil> + {
>> Phil> + char *s = PyString_AsString (py_str);
>> Phil> + len = PyString_Size (py_str);
>> Phil> + thevalue = xmemdup (s, len + 1, len + 1);
>> Phil> + type = builtin_type (gdbarch)->builtin_char;
>> Phil> + Py_DECREF (py_str);
>> Phil> + }
>> Phil> }
>> Phil> Py_DECREF (output);
>> Phil> }
>> Phil> if (thevalue && !string_print)
>> Phil> {
>> Phil> do_cleanups (back_to);
>> Phil> + xfree (encoding);
>> Phil> return thevalue;
>>
>> This is wrong in the lazy string case, because you are returning raw
>> bytes, but the user expects them to be interpreted according to the
>> encoding.
>>
>> We discussed this on irc and I thought the result was that we agreed
>> that in this case we would pretend that a "string" hint was given.
>
> We did. This case is slightly different case from original case we
> discussed in irc (the original was in the non-mi case). Anyway, if
> thevalue is not NULL (and in these cases it won't) it is printed via
> LA_PRINT_STRING (just a few lines further past this patch hunk) and
> the encoding happens at that point.
Oops I spotted the bug just after I sent this. Everything will work if
only string_print is set properly for lazy strings ;) (which you
mentioned ;). Ok, sorry for the noise, I'll set that hint.
next prev parent reply other threads:[~2010-01-11 21:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 14:52 Phil Muldoon
2010-01-08 16:25 ` Eli Zaretskii
2010-01-11 15:40 ` Phil Muldoon
2010-01-11 19:10 ` Eli Zaretskii
2010-01-11 21:08 ` Tom Tromey
2010-01-11 21:30 ` Phil Muldoon
2010-01-11 21:40 ` Phil Muldoon [this message]
2010-01-12 17:02 ` Tom Tromey
2010-01-13 14:49 ` Phil Muldoon
2010-01-13 18:13 ` Tom Tromey
2010-01-13 20:23 ` Phil Muldoon
2010-01-13 20:33 ` Tom Tromey
2010-01-14 21:24 ` Phil Muldoon
2010-01-13 18:24 ` Eli Zaretskii
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=4B4B9ADD.9030200@redhat.com \
--to=pmuldoon@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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