w3wilkes wrote: > Just one comment as an old retired programmer... Murphy's law applies > here "if anything can go wrong, it will". Whatever code is failing > should have tested the operand(s) for validity prior to performing an > operation that has any possibility of failing. The error should be noted > (logged) and then the code should move on.
Absolutely agree with you... This should be implemented by devs. If anyone can raise the feature request (or bug fix), would be great: On this error: Log error and move on: traps: squeezeboxserve[18052] trap divide error ip:7f4f4329fb70 sp:7ffc3b2ebe90 error:0 in Scale.so[7f4f4328c000+73000] ------------------------------------------------------------------------ Superkikim's Profile: http://forums.slimdevices.com/member.php?userid=16821 View this thread: http://forums.slimdevices.com/showthread.php?t=106417 _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
