Getting more info about crashing Live (very likely RNBO-related)
I'm trying to build a M4L device built with RNBO. It's stable in Max environment, but when testing in Live it will frequently/always crash Live.
If it doesn't crash when loading the device, there are some pretty easy reproducible steps I can use to cause the crash. The same / similar steps do not cause crashing in Max environment.
Unfortunately, when Live crashes no crash reports with a backtrace are generated, so I have no insight into what / where the code is crashing. I get only:
In Live's Log.txt, I can find the line with the error, but there's nothing clearly useful before it:
2024-01-17T19:11:32.920553: error: FatalError: Uncaught exception
I've tried setting the "-StackTraces" option in Live's Options.txt, but I don't know if that's a deprecated option as it didn't change anything about the logging output.
Is there any way to get more useful logging or a backtrace out of Live?
Can you give us your support info and are you willing/able to share your patch? It is unclear if you're talking about a rnbo~ based device or a device that uses a rnbo exported compiled max external. Can you elaborate a bit?
Hi Alex, I was really trying to ask a general question about getting debugging info, because otherwise people are just left blindly cutting out / modifying code as guesswork, which is extremely tedious.**
For the specific case I narrowed down the cause of the issue and have filed a bug report, complete with a sample patch to reproduce it. Basically: output from RNBO triggered things in Max and immediately sent input back into RNBO.
The issue happens both with the raw [rnbo~] code as well (I'm 99% certain) with the compiled external, but only in Live and not in Max.
** Someone recently made a forum post about "please make some kind of CLI for exporting projects". The ability to, by command line, export a consolidated .amxd would go great lengths toward alleviating this, even if there isn't an automated way to run tests on .amxd files in Live.