Thanks for the backtrace. It looks like some sort of memory corruption going on. So if you fix the quotes in the <script> tag, the segfault doesn't happen? It's interesting because the SIGSEGV isn't actually happening when working on the corrupt url, we successfully get the 404 and then move on to /shows-page/ url, and the SIGSEGV doesn't occur until trying to convert 'www.[redacted]' to the current locale. Out of curiosity, what is the current locale of the machine?
A valgrind log ( https://wiki.ubuntu.com/Valgrind ) may help, but the bug may be difficult to track down without being easily reproducible.
Thanks for the backtrace. It looks like some sort of memory corruption going on. So if you fix the quotes in the <script> tag, the segfault doesn't happen? It's interesting because the SIGSEGV isn't actually happening when working on the corrupt url, we successfully get the 404 and then move on to /shows-page/ url, and the SIGSEGV doesn't occur until trying to convert 'www.[redacted]' to the current locale. Out of curiosity, what is the current locale of the machine?
A valgrind log ( https:/ /wiki.ubuntu. com/Valgrind ) may help, but the bug may be difficult to track down without being easily reproducible.