RE: Performer out of memory behavior

New Message Reply Date view Thread view Subject view Author view

From: Mark Acosta (macosta++at++magic-earth.com)
Date: 02/07/2001 16:01:55


Yair,

        Yeah, I can probably live with that.

Mark

-----Original Message-----
From: yair++at++polygon.engr.sgi.com [mailto:yair++at++polygon.engr.sgi.com]
Sent: Wednesday, February 07, 2001 5:37 PM
To: macosta++at++magic-earth.com
Cc: info-performer++at++sgi.com
Subject: Re: Performer out of memory behavior

Mark,

> You said that I could just return normally from the handler and the
> result would be a NULL pointer returned from pfMalloc. This is actually
what
> I'd like to do. I would like to give my application the chance to recover
> rather than just exit. For all other resource errors, I'd just let
Performer
> process them normally. It possible to do this?

Not without comparing the error string (and hoping that it won't change in
future Performer releases).

I would write a handler that never exits on FATAL errors. This way, you can
intercept out-of-memory errors. A FATAL error is serious enough that if you
don't exit, your program will crash anyway. Can you live with this ?

-yair

-- 
\_________  \_____  \__    \__  \_____         Yair Kurzion
\_________  \_____   \__   \__  \_____         yair++at++sgi.com
       \__     \__   \____\__      \__   http://reality.sgi.com/yair
       \__          \__  \__                Work: (650) 933-6502
       \__          \__   \__               Home: (408) 226-9771
       \__          \__    \__             
-----------------------------------------------------------------------
 List Archives, FAQ, FTP:  http://www.sgi.com/software/performer/
Open Development Project:  http://oss.sgi.com/projects/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 2b29 : Wed Feb 07 2001 - 16:01:21 PST

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