Re: GError location filename as wide chars

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/ line
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/ line
*** glibc detected *** perl: realloc(): invalid next size: 0x0910d048
======= Backtrace: =========
======= 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, and then go in the test folder,
Data::Dumper prints :
$filename = "/mnt/ramdisk/dirtestwithxF3\x{ef9af}";
the "" comes from, 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 :


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]