On Sun, Oct 18, 2009 at 12:59 PM, Geoff McLane <ubu...@geoffair.info> wrote:
> Hi Vivian,
>
>>> using anything other than the
>>> latest build from Creative Labs?
>
> Well they could for example be using the openal-soft
>  http://sourceforge.net/projects/openal-soft/
> which suggests it is version 1.2.??? And has a CVS
> download, and uses the 'AL' sub-directory!
>
 Software versions and standard versions are two different things, the
OpenAL specification is currently at version 1.1, OpenAL-Soft
implements it.
 Also, that's the wrong place,
 http://kcat.strangesoft.net/openal.html
 is the right one, which doesn't use CVS but git.

>>> cause a crash on exit here
>
> Have not been particularly following ALL the posts on
> this, but with MSVC9's debugger you should be able to
> 'see' _EXACTLY_ where/when this happens...
>
> Quite frequently, in Debug mainly, but can happen also
> in 'random' memory in Release, it is due to things like -
>   if ( _data )
>      delete _data;  // a crash exit
> since, in Debug especially, such a variable is likely filled
> with a debug value, by the MSVC compiler, deliberately, and
> has has never been initialized to NULL in the code...
>
> This is very common... It seems GCC quite frequently ensures
> such 'memory', 'variables' etc are all zeros...
 I believe in debug mode gcc indeed initialises all memory to 0, this
of course should not be done in release mode. Release code should not
depend on the value of uninitialised variables.

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to