Re: Issues with alGenBuffers()

On Thursday 03 December 2009 10:11:24 pm Herbert Elwood Gilliland III wrote:
> Well, this is my first implementation of an OpenAL API from scratch.  I
>  used tutorials found at devmaster.net
> 
> The error I am experiencing is :
> <> <+sacrebleu> Audio ALSoundManager:WAV:alGenSources Error #40963 Invalid
> Value
> <> <+sacrebleu>   alGenBuffers(1, &(sound.Buffer.id));
> if(ALError("ALSoundManager:WAV:alGenBuffers")) ...
>  AL_INVALID_VALUE
> The buffer array isn't large enough to hold the number of buffers
>  requested.

Hi.

What OS are you running on? AFAIK, just the Windows version will actually 
check if the supplied pointer is valid (beyond a simple NULL check, which I 
keep forgetting to add in OpenAL Soft).

If you're on Linux with OpenAL Soft, you can use gdb to find out why the error 
is being generated. First, make sure to have a lib that doesn't have debug 
info stripped out (manually building the lib should provide that, though libs 
provided by package managers are usually stripped). Then run your app with 
gdb, and add a breakpoint on alSetError:

(gdb) break alSetError

It may say it can't find the function, but you can tell it to add the 
breakpoint when the function is loaded later on. Then when you run the app, 
it'll stop execution when the internal alSetError function is called, and you 
can use a backtrace to see why an error is being set.
_______________________________________________
Openal mailing list
[email protected]
http://opensource.creative.com/mailman/listinfo/openal