Subject:
Re: Netscape 6 on Nano-X
From:
Jordan Crouse ####@####.####
Date:
19 Oct 2000 13:39:26 -0000
Message-Id: <39EEF9F2.5F3596E6@censoft.com>
I would say that if two driver routine appear broken, then it must be
something else... :)
I believe this is actually a problem in the engine BLIT that doesn't get
caught until it hits the device dependent blits. If you check
devdraw.c, you will see that the function tries to clip the blit
according to the destination. However, it appears that the routine goes
through and clips the blit for *every* cliping rectangle in the region,
regardless if the blit rectangle actually lives there or not, so that
results in some very screwed up widths and heights. I added in a check
to ensure that the clip area was in the clipping rectangle in question,
and it seems to work.
Jordan
Fu Tony wrote:
>
> Hi Peter,
>
> Thanks a lot. I have the same conclusion. I did the
> same thing and right now I can run Netscape 6 PR3 and
> mozilla M18 on top of nano-X frame buffer mode. BTW,
> fblin8.c have to be changed too. Good job.
>
> Regards,
> Tony
> --- ####@####.#### ªº¶l¥ó¤º®e: >
> >
> > On Thu, 19 Oct 2000, [big5] Fu Tony wrote:
> >
> > > Hi Peter,
> > >
> > > Thanks a lot. I am trying on nano-X X11 verson
> > now. A
> > > little bit progress so far. I can bring up
> > Netscape6
> > > PR3 and ALMOST load URI:www.netscape.com page. But
> > in
> > > the last second nano-X crashed and netscape
> > > terminated. nano-X die at fblin32.c line 133.
> > > I log the O/P it's as follows:
> > >
> > >
> >
> ======================================================
> > > clearing PRIMARY clipboardano-X
> > > XDefaultVisual:
> > > Visual class: TrueColor (4)
> > > id: 32
> > > bits_per_rgb: 6
> > > map_entries: 64
> > > Screen RootDepth: 16
> > > Screen RootVisual
> > > Visual class: TrueColor (4)
> > > id: 32
> > > bits_per_rgb: 6
> > > map_entries: 64
> > > Depth: 16
> > > Visual: 0
> > > Visual class: TrueColor (4)
> > > id: 32
> > > bits_per_rgb: 6
> > > map_entries: 64
> > > setting colormap
> > > setting colormap
> > > freetype_createfont: serif,16 not found
> > > freetype_createfont: sans-serif,11 not found
> > > freetype_createfont: sans-serifb,11 not found
> > > freetype_createfont: sans-serif,10 not found
> > > freetype_createfont: serif,16 not found
> > > freetype_createfont: serif,16 not found
> > > freetype_createfont: serif,10 not found
> > > freetype_createfont: serif,10 not found
> > > freetype_createfont: monospace,13 not found
> > > freetype_createfont: sans-serif,10 not found
> > > freetype_createfont: sans-serif,10 not found
> > > freetype_createfont: sans-serif,10 not found
> > > freetype_createfont: sans-serif,16 not found
> > > freetype_createfont: sans-serif,16 not found
> > > freetype_createfont: sans-serif,16 not found
> > > freetype_createfont: sans-serif,10 not found
> > > freetype_createfont: sans-serif,10 not found
> > > freetype_createfont: sans-serif,10 not found
> > > freetype_createfont: serif,16 not found
> > > freetype_createfont: sans-serif,10 not found
> > > freetype_createfont: sans-serif,10 not found
> > > clearing PRIMARY clipboardear32_blit: Assertion `h
> > >
> > > 0' failed.
> > > Aborted (core dumped)
> > > [root@cr523841-a bin]#
> > >
> >
> =======================================================
> > >
> >
> > Ok, this is a known bug. It is because Mozilla may
> > attempt to render
> > images with a width or a height of zero. One way I
> > found to stop this was
> > to remove the assert commands from the fblin32.c
> > file. The way I did this
> > was wrap the assert.h include in an #if 0, #else
> > then #define assert. ie
> >
> > #if 0
> > #include <assert.h>
> > #else
> > #define assert(what)
> > #endif
> >
> > I am hoping to find a better fix for this.
> >
>
> _________________________________________________________
> Do You Yahoo!?
> µn°O§K¶Oªº @yahoo.com ¤¤¤å¹q¤l¶l¥ó @ http://chinese.mail.yahoo.com
> Get your free @yahoo.com address at http://chinese.mail.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
