Re: gl: warning, mmap failed, got 0xffffffff.

New Message Reply Date view Thread view Subject view Author view

Rob Jenkins (robj++at++quid.csd.sgi.com)
Tue, 16 Dec 1997 14:49:06 -0800


On Dec 16, 3:19pm, G.W. Estep II wrote:
> Subject: gl: warning, mmap failed, got 0xffffffff.
> Any idea what is causing this error?
>
> Running on an Onyx RE2, 2 - R4k CPU, Perfomer 2.0.
>
> The wierd thing about this is the executable and datafiles lived on this
> efs disk and then were copied off, the disk upgraded to xfs and the
> files put back. Even after rebuilding the executable, I still get the
> message in the subject line as the first message out of the program,
> which is based on perfly.
>
> Might I be missing a patch or two? Which ones are the correct ones for
> this machine?

Does the app run OK ? If so I think this is relnoted in the pf 2.x relnotes but
it's a 'collision' between IrisGL and OpenGL, are you loading an Inventor model
in an app running linked with IrisGL ? I think the clash is between the OpenGL
done in Inventor and stuff done by the Performer IrisGL IV loader. If the app
runs OK then the msg is probably harmless. If it's nothing to do with the
Inventor loader thjen perhaps you are mixing IrisGl and OpenGL calls in your
app.

See the Performer web page->FAQs for the right pf install ( version and patches
) for you machine/OS. See the SGI support web pages for the latest recommended
patch sets, off the top of my head, you should make sure you have the RE2 gfx
roll up 2038.

Cheers
Rob

-- 
________________________________________________________________
Rob Jenkins mailto:robj++at++sgi.com
Silicon Graphics, Mtn View, California, USA
=======================================================================
List Archives, FAQ, FTP:  http://www.sgi.com/Technology/Performer/
            Submissions:  info-performer++at++sgi.com
        Admin. requests:  info-performer-request++at++sgi.com

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:56:26 PDT

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