mattgilbertnet

Is there a way to add procedure labels to your externals to make crash reports more informative?

I've been developing externals in M4L devices for a little while, and running into sort of difficult-to-reproduce crashes, with crash reports that don't look too similar. Is there a way to make them more informative, in case one of my externals is the culprit?

Is there a way to add procedure labels to your externals to make crash reports more informative?
I've been developing externals in M4L devic

procedure-labels-for-crash-reports

 when I came across this line: "Thankfully, the developer of the aforementioned plug-in (

) was nice enough to include procedure labels that indicate each task." Is there a way to label your externals such that crash reports are more informative?

For a little context, I was reading this article when I came across this line: "Thankfully, the developer of the aforementioned plug-in (CF/X) was nice enough to include procedure labels that indicate each task." Is there a way to label your externals such that crash reports are more informative?

procedure labels for crash reports