Re: mongoose problem...

New Message Reply Date view Thread view Subject view Author view

David Popeck (david++at++cdirect.co.uk)
Sun, 17 Oct 1999 04:09:26 +0000

> Note the beta for
> Performer on Linux is known to work with Mesa3.0 and Mesa3.1beta1.
> We've had troubles with Mesa3.1beta2. Mesa3.1beta3 seems to work fine in
> most cases, although we've had one problem report of it core dumping in
> glGetString(). This is being investigated.
>

I have encountered this problem when running Mesa 3.1b3 with a Voodoo3 card.
It appears that glGetString is being called before Mesa has a GL context setup and
the reference to *CC->API.GetString is failing because CC=NULL. The following
is a quick fix to Mesa to get things working without a full debug build.

I don't know if this is a problem with mongoose or with Mesa. Either way this gets things
running.

If have to say - Great work by the performer team, truly amazing to see the town demo
running on my PC. The really sad thing is the PC performance beats my O2 :-(
Oh well the price of progress I guess. :-)

Regards

David Popeck

----- cut here -----
*** api1.c Sun Oct 17 05:00:27 1999
--- api1.c.new Sun Oct 17 05:05:52 1999
***************
*** 1399,1405 ****
  const GLubyte * GLAPIENTRY glGetString(CTX_ARG GLenum name )
  {
     GET_CONTEXT;
! CHECK_CONTEXT_RETURN(NULL);
     return (*CC->API.GetString)(CC, name);
  }

--- 1399,1411 ----
  const GLubyte * GLAPIENTRY glGetString(CTX_ARG GLenum name )
  {
     GET_CONTEXT;
! /* Quick fix to get Performer running without compling everything as debug*/
! if (!CC) { \
! if (getenv("MESA_DEBUG")) { \
! fprintf(stderr,"Mesa user error: no rendering context.\n"); \
! } \
! return (NULL); \
! }
     return (*CC->API.GetString)(CC, name);
  }

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Sat Oct 16 1999 - 20:16:14 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.