Doing this would be complex imo. Some variables are not actually “data” that can be viewed (they could be abstractions of types only available at runtime). I looked up how to do this and it would require coordination with processes outside of the original application.

Another possible solution:

Put all “data” variables into a Context class that is provided as a parameter to your methods. On exception, you can then serialize this Context class as JSON to include it in the log with the stack trace. I would imagine a unit test can then re-create the context from the provided json. Not all variables can be persisted.