I've developed an mxj object that is part of a Max/Jitter patcher. The mxj object is multi-threaded and runs fine in the Windows XP environment on machines that are multi-core or single CPU.
A problem occurs in the Mac environment running the patcher. Shortly after the patcher begins execution, Max locks up and becomes unresponsive. The "spinning wheel" appears and never goes away. Other applications are accessible and run fine during this condition.
I'm fairly positive that my mxj object is the culprit. Since I know that the Java version on the Mac machine is earlier than the Java version used in the Windows environment, I think it's likely the mxj object may be dependent upon a Java facility that's not present on the Mac machine. If that's true, I was hoping an indication of what is wrong would be written to the Max window prior to Max becoming unresponsive.
Is there a way to force what's written to the Max window to also be written to a log file? The Max window is hidden by the patcher and cannot be brought to the fore because Max is unresponsive.
Thanks in advance....Steve