In your methods that are catching exceptions, they're continuing after you 
catch the exception
which is not what you want in general.  When you catch an exception the 
program isn't terminated
unless you throw one in the catch clause.  Catching an exception means that 
you're going to do
some sort of recovery in general, unless you throw another one in the catch 
clause.  You could
also close file descriptors in the catch clause and then rethrow the 
exception that you caught.

Unless you're going to do something when you catch the exception you should 
just let the
exceptions terminate the program, meaning that you'll need to add the 
appropriate throws clauses.
That should also give you a stack trace which may be helpful.  And it will 
include the name of
the exception, and possibly the reason.

I did a google search on javax.sound.sampled.LineUnavailableException and 
there were some
queries about that exception on StackOverflow.  Try doing a google search 
and see what you find.


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to