There was a really old thread with the exact same stack trace coming from google's syscaller fuzzing BOT. It seems that the BOT was right =o).
I have replied with this stack trace, telling them I got a way to reproduce the issue:
https://<email address hidden>/
and will monitor the thread.
There was a really old thread with the exact same stack trace coming from google's syscaller fuzzing BOT. It seems that the BOT was right =o).
I have replied with this stack trace, telling them I got a way to reproduce the issue:
https://<email address hidden>/
and will monitor the thread.