Version
v19.4.0
Platform
Linux AVRAST1790 5.19.0-30-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Fri Jan 6 15:40:20 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
test
What steps will reproduce the bug?
When running some failing code that throw an exception, the stack trace shows the private methods that the code has passed on, but when the same exception is thrown as part of one test of the new built-in test module, stack traces for private methods are removed, not sure if on purpose or by an error (I think the later, since it's important info for debuging).
How often does it reproduce? Is there a required condition?
Always that I run it.
What is the expected behavior?
All stack traces shown on errors thrown when running the test module, including the calls to private methods.
What do you see instead?
Stack traces for private method calls are missing on the stack traces.
Additional information
No response