[fpc-devel] WideString vs UnicodeString / len in char vs byte / *nix vs windows
lazarus at mfriebe.de
Thu Apr 25 17:54:41 CEST 2019
On 25/04/2019 17:37, Michael Van Canneyt wrote:
> On Thu, 25 Apr 2019, Sven Barth via fpc-devel wrote:
>> Am 25.04.2019 um 15:41 schrieb Martin:
>>> Looking at https://bugs.freepascal.org/view.php?id=35359
>>> and the latest comments (see end of mail)
>>> Is it correct, that "widestring" here has 2 meanings?
>>> - the "widestring" that has length in bytes (windows bstr)
>>> - "widestring" as a typename / alias
>>> And apparently then on *nix, "widestring" is just an alias (to
>>> So using the type with the name of "widestring" on *nix will compile
>>> to a type that has length in chars?
>>> At least my test app, seems to imply this.
>> Correct. On non-Windows platforms WideString is always an alias to
>> UnicodeString. The distinctive WideString type only exists on Windows
>> platforms as it relies on Windows specific functionality.
> This is only about generated debug information, I suppose ?
There for the debugger the bytes have to be "div 2" or "shr 1", which
leads to above mentioned issue, that (if dwarf 3 is used) any debugger
(gdb, fpdebug) will show the first half of any unicodestring. (because
the unicodestrings length in char is also divided by 2)
More strangeness though.
The code that adds the "shr 1" is actually not used for windows-like
widestrings (only tested dwarf-3, not tested dwarf-4 / dwarf 2 does not
use it at all; not supported in dwarf 2).
And the commit that adds the "shr 1"
> Revision: 12444
> Author: jonas
> Date: 27 December 2008 22:43:45
> + append_block1() to add extra block DW_FORM_block1 attributes to
> a dwarf entry
> - (dwarf3) removed stride size from dynamic array entries because
> it's not required there (the stride always equals the element size)
> + (dwarf3) added "allocated" attribute for dynamic arrays
> + (dwarf3) added generic implementation of string support for dwarf3,
> which no longer depends on the hacked fake record type in gdb's
> Pascal support. Includes support for all string types, except for
> winlike widestrings (because I don't know how to extract the
> length from them)
actually states, that it excludes them: "except for winlike widestrings
" (or at least that what I guess this means)
However, that commit actually also adds the test for "if
(chardef.size=1) then" to decide if "shr 1" should be added.
I do not know, if widestrings actually ever were handled by this code
(maybe at the time of above commit), or what other reasons the "shr 1"
had at the time.
In any case the patch (fixed patch) available on the mantis issue does
fix the problem for unicodestring (and for the widestring alias on *nix).
As the code is currently not used for winlike widestring (or at least I
could not trigger it), I can not tell if it would affect such.
More information about the fpc-devel