Sorry for the delay but this was gonna be a long email and our support channel is quite busy these days.
The short answer is yes: you can use both strategies for your project (this is not IoT / ARM / Raspberry Pi) specific and we even have customers using this for many years (this feature is in the product at least since 1997).
If I were you, before thinking how to integrate this into you project, I would start with a fresh 9.2.2 image and the Seaside Traffic Light example. That code is even shipped VAST so you can re-watch and follow the exact steps I did in the IoT demo [1] as well as at Smalltalks 2019 [2]. I recommend watching Smalltalks one if you didn't (the presentation at ESUG 2019 wasn't recorded...). I have also written a blog post [3] that will likely be of help.
In addition to that, we have Instantiations official documentation with steps by steps instructions to use both strategies. I would read the whole "Packaging a Smalltalk image" chapter [4] and the pay special attention to the examples [5] and [6].
Once you are able to package those examples and be able to use the stack dump and the remote debugger, I would then take a look at the code that supports that. For this, the easiest way is to browse the code in your passive image where you have loaded those features. I would look at the classes AbtInteractiveDebugStartUp and AbtStackDumpStartUp. You can see what those startUp classes do and then you could even do something similar outside of the StartUp class if that's what you want.
If you look at the code, you will see that the remote debugger, if there is an error, it fallbacks and uses the stack dump. And the stack dump, if fails, fallbacks to walkback. Something I would do for a production system is that no matter how I debug the error, I would *always* ALSO dump into a walkback. This is just in case you can't debug the binary later because of whatever reason, you are sure you at least have the walkback. In other words, I wouldn't REPLACE the walkback, but just potentially ADD the stack dump.
One final comment...all the example you will see are using XD packaging and headless images. This would be different with fat client / desktop applications. I think the stack dump should work fairly easily and we can improve it if necessary. But the remote debugger would be much more complicated to make it work in that scenario.
I guess with all this information you have a lot to chew on. But keep me posted of your progress.
Best regards,
Mariano
[1] https://youtu.be/wCw0ZLStDzA
[2] https://youtu.be/u2AVD_-7E8k
[3] https://dev.to/martinezpeck/it-s-2019-stop-reading-text-and-start-debugging-2460
[4] https://www.instantiations.com/docs/922/wwhelp/wwhimpl/js/html/wwhelp.htm#href=sv/server97.html
=====
--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to va-smalltalk...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/va-smalltalk/ed5b99cb-f45d-4157-9c2b-b41144528cbcn%40googlegroups.com.