On Thu, Aug 24, 2006 at 06:47:22PM +0200, Abdelrazak Younes wrote:

> Enrico Forestieri wrote:
> > I have compiled a Cygwin version of LyX/Qt4 using the native GUI (no X11)
> > and now I see the chinese characters mentioned by Abdel when I load
> > an old document. I also get a lot of messages on the console:
> > 
> > Error returned from iconv
> > EILSEQ An invalid multibyte sequence has been encountered in the input.
> > When converting from UCS-4 to UCS-2.
> > Input: 0xff 0xff 0xff 0xa2 
> > 
> > This was not the case with Qt3 where the characters were simply hollow
> > squares on screen. However, when I start a new document the characters
> > are shown correctly.
> 
> The attached patch at least make LyX show normal text correctly.

Yes, that made it, thank you. Also for Qt3. Math and inset titles are
displayed as funny "?" symbols, though.

> > LyX also crashes when quitting, but I don't know if this is related to
> > the patches I applied to Qt4 or if it is a LyX problem. Anyway, all
> > Qt4 examples compile and run just fine.
> 
> Backtrace?
> 

Here it is:

Program received signal SIGSEGV, Segmentation fault.
0x00a26660 in inflate_fast ()
(gdb) bt
#0  0x00a26660 in inflate_fast ()
#1  0x009199f5 in inflate_fast ()
#2  0x008cb00f in inflate_fast ()
#3  0x007a16d9 in inflate_fast ()
#4  0x610f4903 in __call_exitprocs () from /usr/bin/cygwin1.dll
#5  0x610dfe48 in exit () from /usr/bin/cygwin1.dll
#6  0x61004e41 in cygwin_exit () from /usr/bin/cygwin1.dll
#7  0x61006170 in dll_crt0_1 () from /usr/bin/cygwin1.dll
#8  0x61004416 in _cygtls::call2 () from /usr/bin/cygwin1.dll
#9  0x00000000 in ?? ()

It seems that the crash is occurring inside the cygwin dll, though.
I don't know what is going on here. However, this may well be my fault
as I had to merge the X11 and Win32 Qt4 distributions from Trolltech
in order to build a cygwin Qt4 using native windows graphics but
otherwise posix functions for anything else. After all, I only spent
a couple of nights to forward port to Qt4 the changes I had devised
for Qt3 ;-)

-- 
Enrico

Reply via email to