Closed jschlatow closed 2 months ago
Wow, that's simply amazing! I'm impressed how the concepts that evolved with the Sculpt-on-target debugging work are so well applicable to Goa.
Wow, that's simply amazing! I'm impressed how the concepts that evolved with the Sculpt-on-target debugging work are so well applicable to Goa.
My next step is to integrate the debug monitor into goa testbed with the goal of running gdb on the local system and connect it to the remote Sculpt target. I'm curious how well this plays out. In this scenario, the separation of binaries and debug info is really beneficial. It would be quite annoying to wait for debug symbols being uploaded to the remote test system.
The solution seems to fall so natural into place. If it works out as you intend, this will rock!
This looks really useful :+1:
I added debugging support for the sculpt run target with the above commit series that I merged to staging. This is accompanied by a new version of goa_testbed found in my depot index. I'm going to write an article for genodians.org with detailed instructions.
The changes entered the master branch. Detailed instructions will soon be available on genodians.org.
The above commit series implements support for handling dbg archives (download, export, publish) in Goa.