33544 2010-01-12 12:00:37 -0800 fast/xsl/exslt-node-set.xml crashed on Gtk Linux 64-bit Debug Bot 2024-02-05 07:25:05 -0800 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) PC OS X 10.5 RESOLVED CONFIGURATION CHANGED P2 Normal --- 33295 1 eric webkit-unassigned ahmad.saleem792 gustavo oldest_to_newest 179925 0 eric 2010-01-12 12:00:37 -0800 fast/xsl/exslt-node-set.xml crashed on Gtk Linux 64-bit Debug Bot Sadly the stderr seems to have no indication of why it crashed: http://build.webkit.org/results/GTK%20Linux%2064-bit%20Debug/r53140%20(2324)/fast/xsl/exslt-node-set-stderr.txt encoding error : input conversion failed due to input error, bytes 0xA0 0xDB 0xAC 0x02 encoding error : input conversion failed due to input error, bytes 0xA0 0xDB 0xAC 0x02 I/O error : encoder error 181292 1 eric 2010-01-15 11:41:06 -0800 Another crash: http://build.webkit.org/results/GTK%20Linux%2064-bit%20Debug/r53334%20(2434)/fast/xsl/exslt-node-set-stderr.txt Do we think this is a libxslt crasher (or whatever the Gtk build uses), or is this a webkit bug needing debugging? I would expect this should be easy to repro locally. A stack trace from a debug reproduction would help. 2010648 2 ahmad.saleem792 2024-02-05 07:25:05 -0800 We don't have any platform specific expectation for this test, searched via `searchfox.org` using `wubkat`. Marking this as 'RESOLVED CONFIGURATION CHANGED'.