gzz-dev
[Top][All Lists]
Advanced

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

Re: [Gzz] FenPDF errors with ATI


From: Tuomas Lukka
Subject: Re: [Gzz] FenPDF errors with ATI
Date: Thu, 7 Aug 2003 18:27:01 +0300
User-agent: Mutt/1.5.4i

On Thu, Aug 07, 2003 at 04:29:19PM +0300, Tuukka Hastrup wrote:
> 
> This is what I get running FenPDF with ATI Radeon 9500:
> ***
> EXCEPTION WHILE UPDATING!
> java.lang.Error: Invalid paper gotten back: npasses 3 
> address@hidden
>       at 
> org.fenfire.spanimages.gl.PlainPaperMaker.makePaper(PlainPaperMaker.java:99)
>       at 
> org.fenfire.spanimages.gl.DefaultSpanImageFactory.getSpanImageVob(DefaultSpanImageFactory.java:109)
>       at org.fenfire.view.PageSpanLayout.page(PageSpanLayout.java:79)
>       at org.fenfire.view.PageSpanLayout.<init>(PageSpanLayout.java:110)
>       at org.fenfire.view.PageNodeView.f(PageNodeView.java:51)
> ***

Yes - since ATI doesn't do pbuffers, we give a full paper, never
optimizing.

The code in makePaper should be adapted to deal with this by adding
another pass, maybe.


> Trying to run fenfire tests hangs the X server until I "kill -9" some java 
> thread (using -Dvob.api=awt the tests pass):

Odd...

> org.fenfire.spanimages.gl.spanimages.testPlainPaper (Test that plain paper 
> renders right.)... 
> An unexpected exception has been detected in native code outside the VM.
> Unexpected Signal : 11 occurred at PC=0x0
> Function=[Unknown.]
> Library=(N/A)
> 
> NOTE: We are unable to locate the function name symbol for the error
>       just occurred. Please refer to release documentation for possible
>       reason and solutions.
> 
> 
> Current Java thread:
>       at org.nongnu.libvob.gl.GL.renderImpl(Native Method)
>       at org.nongnu.libvob.gl.GL.render(GL.java:899)
> 
> 
> Might be a driver problem as I get some random SIGSEGVs elsewhere, but 
> this one seems systematic.

Ah, yes, I remember now - ATI doesn't support loading compressed
textures. Their driver claims to have the extension but using the entry
point causes a crash. BAD.


> In libvob's test-gl, only failure seems to be the following:
> 
> ***
> test.vob.gl.specialpaper.testGraph
> Traceback (most recent call last):
>   File "./test/vob/gl/specialpaper.test", line 77, in testGraph
>     checkAvgColor(50, 250, 4, 4, (255,0,0))
>   File "/home/tuukka/cvs/Fenfire/libvob/test/tools/gfx.py", line 94, in 
> checkAvgColor
>     raise msg
> ((255, 0, 0), [0.0, 0.0, 0.0, 255.0], ':', 50, 250, 4, 4)
> ***

That means it should be painted red but is black.

        Tuomas




reply via email to

[Prev in Thread] Current Thread [Next in Thread]