Yes, if you can only see assembly it is because it is optimized away. A Debug build might allow you to inspect that variable.
Another alternative is, if you are building the engine from source, surround the method with the macros
UE_DISABLE_OPTIMIZATION
UE_ENABLE_OPTIMIZATION
That will disable optimization just for the surrounded method (remember revert this change after you are done debugging)
That said, it is unclear to me why it would fail only when packaged from specific machines.
If not done already, I would try to sync the project from scratch in new location in the affected machine, and then do a new build/package. This is to discard any potential content issue in the project due to a bad sync.
Lastly, if I read the log snippet right, is the component that always fail named ProSaveComponent? If so, does that component have custom serialization code? If the answer is yes, there might be an issue with the implementation of that component.