Re: [Chromium-users] segmentation fault in crserver.

[James S. <arr...@gm...>]

While you got Sauerbraten running, you broke tuxracer. I was looking that
the cvs diff to see what you did, and I noticed this
        case GL_UNSIGNED_SHORT:
                {
                        const GLushort *p = (const GLushort *) indices;
                        for (i=0; i<count; i++)
                                crPackExpandArrayElement(p[i], c);
                }
                break;
        case GL_UNSIGNED_INT:
                {
                        const GLushort *p = (const GLushort *) indices;
                        for (i = 0; i < count; i++)
                                crPackExpandArrayElement(p[i], c);
                }
I find that replacing const GLushort *p = (const GLushort *) indices; with
const GLuint *p = (const GLuint *) indices; for case GL_UNSIGNED_INT will
fix tuxracer (which is a mission critical application for many people).

Thank you for your time,
James Steven Supancic III

On 8/4/06, James Supancic <arr...@gm...> wrote:
>
> The application is still very slow, but it no longer causes segmentation
> faults =) I am going to toy with some configuration options and see if I can
> speed it up a bit that way.
>
> Thank you very much.
>
>
> Thank you for your time,
> James Steven Supancic III
>
> On 8/4/06, Brian Paul <bri...@tu...> wrote:
> >
> > James Supancic wrote:
> > > I think you may have left the deffintion of
> > > crStateUseServerArrayElements out. I did a cvs checkout to be sure, I
> > > tried to build, it failed. so I did
> > > grep -ri crStateUseServerArrayElements ./*
> > > and it returns one line
> > > ./spu/tilesort/tilesortspu_client.c:
> > > crStateUseServerArrayElements()) {
> > >
> >
> > Sorry, I forgot to check in a couple files.  Try again.
> >
> > -Brian
> >
>
>