Comments on: Matlab compiler bug and workaround

By: Yair Altman

Yair Altman — Mon, 02 Feb 2015 13:39:27 +0000

In reply to Tom. @Tom - thanks for the update

By: Tom

Tom — Mon, 02 Feb 2015 13:37:20 +0000

Hi,

i compiled the code snippet on Matlab Compiler 32 bit R2011b, R2012a, R2012b, R2013a and R2013b. The bug disappeared with R2012b when they changed the desktop GUI (Version 8.0).

By: Yair Altman

Yair Altman — Sat, 31 Jan 2015 18:43:01 +0000

In reply to Arthur.

@Arthur – chapter 8 of my Matlab-Java Programming book gets you partly there; the rest you can get by some extra digging. This seems to be a niche issue that would only be of interest to a few people, so I’m not sure I’ll write a dedicated article about this in the near future…

By: Arthur

Arthur — Thu, 29 Jan 2015 16:35:40 +0000

Would be very interested to read about “…well, actually we do have access to a scaled-down desktop for minimal debugging using some undocumented internal hooks..”. Is this topic by any chance covered in one of your books?

By: Yair Altman

Yair Altman — Wed, 28 Jan 2015 20:14:24 +0000

In reply to Ty Cumby. @Ty - thanks for the update

By: Ty Cumby

Ty Cumby — Wed, 28 Jan 2015 20:09:33 +0000

I compiled the code snippet on Matlab 2014b (64-bit) and 2013a (32-bit) this bug does not seem to be present, thankfully. In both cases the compiled *.exe correctly reported the line number of the offending line.