Re: GError location filename as wide chars

[Quentin Sculo <squentin free fr>]

On Thu, 2009-02-26 at 11:02 +1100, Kevin Ryde wrote:
> > get_preview_filename : doesn't work
>
> Yes, that one's bad for me too
>
>     *** unhandled exception in callback:
>     ***   Invalid byte sequence in conversion input
>
> I guess it returns bytes, but gperl_sv_from_filename() doesn't like
> them.  Should they be left alone, as a plain "char*" return?
I think so

> > more details about the crashes
>
> Just the conversion error "Invalid byte sequence" as above, or worse?
much worse, full crash, very random, the most common message is :
Malformed UTF-8 character (overflow at 0xe6a6c974, byte 0x65, after
start byte 0xff) in subroutine entry
at /usr/lib/perl5/5.10.0/i386-linux-thread-multi/Data/Dumper.pm line
190.
Malformed UTF-8 character (overflow at 0xc9e00000, byte 0x19, after
start byte 0xff) in subroutine entry
at /usr/lib/perl5/5.10.0/i386-linux-thread-multi/Data/Dumper.pm line
190.
*** glibc detected *** perl: realloc(): invalid next size: 0x0910d048
***
======= Backtrace: =========
/lib/i686/libc.so.6[0xb7cbac24]
/lib/i686/libc.so.6[0xb7cbe8e1]
/lib/i686/libc.so.6(realloc+0x10c)[0xb7cbf63c]
/usr/lib/perl5/5.10.0/i386-linux-thread-multi/CORE/libperl.so(Perl_safesysrealloc+0x4c)[0xb7ed9e2c]
======= Memory map: ========
...

I tried commenting the Data::Dumper line, it makes the crash much more
rare, but it still happens
I noticed that when I select foo2.pl, and then go in the test folder,
Data::Dumper prints :
$filename = "/mnt/ramdisk/dirtestwithxF3\x{ef9af}o2.pl";
the "o2.pl" comes from foo2.pl, it shouldn't be there, it shows that the
string is longer than it should and includes garbage memory.

This is on a mandriva 2009.0, with :
gtk+2.0-2.14.3-2mdv2009.0
libglib2.0_0-2.18.1-1mdv2009.0
perl-Gtk2-1.200-1mdv2009.0
perl-Glib-1.200-1mdv2009.0

Quentin