I’m getting a hard crash on Serial.Write( “some string” )
It’s on Mac OSX and i find it hard to find a solution to this.
DebugMyApplication crashes, UnHandledException is not being raised.
Xojo doesn’t report anything, only my mac (eg “Report to Apple” with a stacktrace).
It doesn’t really matter if i trow a string or “”
Anyone else seeing this? Or has some tips on getting a solution?
Can you post the crash report somewhere?
You can always run into an out of memory situation.
Or sometimes the underlaying C++ object is destroyed too early by a bug in reference counting.
where does your mail address start with?
[quote=237626:@Christian Schmitz]You can always run into an out of memory situation.
Or sometimes the underlaying C++ object is destroyed too early by a bug in reference counting.[/quote]
Ok thanks, that could be a problem.
I’m using Xojo.core.memoryblock with about 5 or more (to 10) bytes.
They are converted to Text using ASCII encoding then written to the serial port.
But, the crash is only just before i write to the serial port.
- Connect button does it’s work, no crash here.
- Write button action event crashes the app, no response from xojo (no exceptions etc).
- System.Debuglog seems to log nothing perhaps it happens in my subclass creating the memoryblock in a shared method.
- App is 32 bit
I’ll have another look, try to make it all properties to the window instead of local scope.
post it in feedback - probably the best option
or email it to @xojo.com