Crash VM doesn't give name (method/event) and line number problem

rgb

Summary

Objo Studio Version

Operating System

Select the operating system(s) affected as tags for this post.

Steps To Reproduce

Expected Result

Actual Result

Screenshots, Logs, Or Sample Project

DrScott

When running my app, the console displayed "Error -- App exited with code 1", but did not indicate where the error was, making debugging impossible.

rgb

DrScott
true, objo doesn't catch correctly some crash but it's version 1.0 we need to be patient.....

Garry

DrScott If you supply an example project I can figure out why more info wasn't available and patch it if possible.

rgb

It's also great if in future version when app crash, objo jump in bottom toolbar to "Output" button
for see directly the code error listing without user intervention

DrScott

I’m not sure that I can pare down this project into a small example project. I’ve been rewriting one of my Xojo projects in Objo to put Objo through its paces. I’m currently narrowing down the site of the crash with breakpoints.

I could send you the project, but I don’t want to send it through the forum since I don’t want the source code to be publicly available. I’m working towards submitting the Swift/SwiftUI version of this app to the iOS App Store. Is there another way I could send it to you?

Garry

DrScott

If you're happy to send the project to me you can email it to

contact@objo.dev

If the source as-is fails with a runtime error I'll inspect the byte code and try to pin down what's happening and how to better catch the error at compile time.

Garry

Fixed in the next release:https://feedback.objo.dev/bug/282

I have made significant improvements to how the compiler analyses projects before running and how runtime errors are reported.