Re: subclassing, C++ API, realloc(0) and so on ...

New Message Reply Date view Thread view Subject view Author view

Angus Dorbie (dorbie++at++sgi.com)
Mon, 01 Feb 1999 13:32:32 -0800

This leaves the impression that there was some incompatibility across
platforms with Performer code but this was most likely a bug in your
application which never surfaced on the other platform. There is always
a chance of this happening to any piece of software with a platform
change or an OS upgrade.

You seem to have fixed this now, so do you know what did you do to get
rid of the problem?

Cheers,Angus.

Marc Erich Latoschik wrote:
>
> Angus Dorbie wrote:
> >
> > An Octane is a dual CPU system and an IMPACT is a single CPU.
> >
> Yep, of course. But not mine ;).
>
> > In effect you were porting a single threaded application which had been
> > written over a period of 3 years to a multiprocessor system.
>
> The application itself was multithreaded from the beginning. I had to do
> lots of
> serial and multicast input and wanted to avoid blocking. That is why i
> started
> the Performer and pthreads thread a few weeks back.
>
> >
> > The realloc(0) problem was probably related to making draw calls in the
> > application.
>
> *SIGH* Thats what i thought too, after me (and some collegues) looked
> over the code
> at least 10 times, i am quite sure there were no draw calls in the app.
> E.g. running
> the ported one in APPCULLDRAW should have worked then but didn't.
> Anyway, lets not cry over history :),
>
> >
> > It's fair to compare your porting effort to the difficulty you'd have
> > had efficiently exploiting your OCTANE multi-processing without
> > performer. Despite your experience I expect that Performer was in fact a
> > big help to you in this respect.
>
> Well, to be honest, i can't really admit that. It wasn't the first
> multi-processing
> step i did. And like you can see, there was no second node in my machine
> anyway.
>
> >
> > I think your suggestions are great, I expect everyone who has
> > implemented a sizeable performer application has encountered similar
> > problems and solved them independently.
>
> Yes, i think i will start soon and give a few explanations about what
> kinds
> of classes i used in which context.
>
> >
> > Cheers,Angus.
> >
> Admin. requests: info-performer-request++at++sgi.com
> 

-- 
"Only the mediocre are always at their best." -- Jean Giraudoux


For advanced 3D graphics Performer + OpenGL based examples and tutors:
http://www.dorbie.com/

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Feb 01 1999 - 13:32:36 PST

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