On a second thought
As this test has been corrected to cope with a kernel without CONFIG_STACKTRACE enabled.
I think this should be enough to close this bug.
If we ever need a discussion / tracking bug for enabling CONFIG_STACKTRACE or not, we can have a new bug for it.
On a second thought
As this test has been corrected to cope with a kernel without CONFIG_STACKTRACE enabled.
I think this should be enough to close this bug.
If we ever need a discussion / tracking bug for enabling CONFIG_STACKTRACE or not, we can have a new bug for it.
I will close this bug.
Thanks!