On Sat, Jul 19, 2008 at 3:04 PM, Andrzej Giniewicz <[EMAIL PROTECTED]> wrote:
>
> Hi again,
>
> was trying to track that segfault in tachyon doctest, it happens
> during show(t) in "texture" example, that's in:
>
> t = Tachyon(camera_center=(2,5,4), look_at=(2,0,0), raydepth=6)
> t.light((10,3,4), 1, (1,1,1))
> t.texture('mirror', ambient=0.05, diffuse=0.05, specular=.9,
> opacity=0.9, color=(.8,.8,.8))
> t.texture('grey', color=(.8,.8,.8), texfunc=3)
> t.plane((0,0,0),(0,0,1),'grey')
> t.sphere((4,-1,1), 1, 'mirror')
> t.sphere((0,-1,1), 1, 'mirror')
> t.sphere((2,-1,1), 0.5, 'mirror')
> t.sphere((2,1,1), 0.5, 'mirror')
> show(t)
>
> I noticed that it happens for texfunc 3 and 5 and only if there is at
> least one sphere with mirror material (they work when there is no
> mirror sphere in scene)... I cannot say how long it is like that, it
> was 3.0.4 when I triggered doctest failure in ssmod and was looking
> into any wrong output in test.log when I found it... btw - other
> texfuncs that don't include images (7,8,9) and those two so (3,5)
> works, for example I'm able to get image with texfunc=1...
>
> I don't know if it helps, it can be something in tachyon by itself, if
> yes it can be good idea to mention it in documentation of "texfunc"
> and/or change doctest to use for example texfunc=1?I can't replicate this segfault on either OS X or Linux. Could you remind me of precisely what hardware/OS you're using and whether or not you built from source or used a pre-compiled binary. Also, I think it is better to fix segfaults than to just document them. William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
