Re: Sudden X/Performer problem

New Message Reply Date view Thread view Subject view Author view

Fred Clyne (rock.csd.sgi.com!sgi.com!uunet.uu.net!ds9!octave!fred)
Wed, 8 Jan 1997 13:04:29 -0500

On Jan 7, 5:57pm, Christopher R Volpe wrote:
> Subject: Sudden X/Performer problem
> Hi folks-
> I was in the middle of debugging a perf application (purely
> application-level changes, nothing specifically performer-related), when
> all of a sudden my app started dying upon startup with the following
> error:
>
> PF Warning/Internal(12): pfWindow::openNewNoPort() - null visual.
> X Error: 0
> Request Major code 0 ()
> Error Serial #33
> Current Serial #15
> Exit 1
>
> I'm running Performer 2.1 on an Irix 6.2 InfiniteReality engine. Anyone
> have any ideas on what might be causing this?
>
> Thanks in advance.
>
> -Chris
> --
>
> Chris Volpe Phone: (518) 387-7766
> GE Corporate R&D Fax: (518) 387-6560
> PO Box 8 Email: volpecr++at++crd.ge.com
> Schenectady, NY 12301 Web: http://www.crd.ge.com/~volpecr
> =======================================================================
> List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
> Submissions: info-performer++at++sgi.com
> Admin. requests: info-performer-request++at++sgi.com
>-- End of excerpt from Christopher R Volpe

>From the Performer 2.2 Beta Release Notes:

o 6.2 OS bug with shared arena placement

        An obscure bug in IRIX 65.2 with default placement of the shared arena
        can cause programs to die due to lack of heap space for malloc.
        Typcially the program will die during X or GL initialization with
        a message like [what you stated above].

WAR: through the environment variable PFSHAREDBASE or in with
        pfSharedArenaBase() before pfInit(), explicitly set the address of the
        arena so that it is not too close to the heap and does not collide
        with other DSOs. An address that has worked with programs exhibiting
        the problem that are very close to perfly is: 0x18000000.

        ex: pfSharedArenaBase(0x18000000); or
            setenv PFSHAREDBASE 0x18000000

        If this address is not sufficient, run again with par [they had an
        example earlier: par -s -i -SS prog options] and the following
        environment variables set:
                setenv _RLD_PATH /usr/lib/rld.debug; setenv _RLD_ARGS -v
        and redirect all output to a file. Look for the addresses of the
        mmap() calls and of address of DSO load actions to find a free
        address range in which to place the arena. Compiling with some
        libraries statically can make this operation easier.

Whew! I hope I don't run into this bug. Hope this helps.

-- 


Fred Clyne


Cambridge Research Associates      office: 703-790-0505 x 7211
1430 Spring Hill Road, Suite 200   fax:    703-790-0370
McLean, VA 22102                   email:  fred++at++cambridge.com


=======================================================================
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:54:17 PDT

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