RESOLVED FIXED 66965
run-webkit-tests -2 does not show stacktraces for crashes on Qt
https://bugs.webkit.org/show_bug.cgi?id=66965
Summary run-webkit-tests -2 does not show stacktraces for crashes on Qt
WebKit Review Bot
Reported 2011-08-25 11:45:36 PDT
run-webkit-tests -2 does not show stacktraces for crashes on Qt Requested by eseidel2 on #webkit.
Attachments
Eric Seidel (no email)
Comment 1 2011-08-25 11:53:01 PDT
In NRWT crashlog discovery can be found here: http://trac.webkit.org/browser/trunk/Tools/Scripts/webkitpy/common/system/crashlogs.py For ports which spit out the crash log to stderr the crash handling is inside the driver, I think.
Eric Seidel (no email)
Comment 2 2011-08-25 11:54:13 PDT
Note that run-webkit-tests -2 uses ORWT at the moment. But if we're going to add this feature, we might as well add it to NRWT. ORWT is soon to be dead. :)
Eric Seidel (no email)
Comment 3 2011-10-21 00:17:34 PDT
Is this still an issue? run-webkit-tests -2 switched to using new-run-webkit-tests tonight. If Qt is dumping the crash log to stderr, we'll display it. :)
Csaba Osztrogonác
Comment 4 2011-10-21 00:25:22 PDT
I don't know ... But Qt uses NRWT for WK2 testing long time ago.
Balazs Kelemen
Comment 5 2011-10-21 04:08:53 PDT
I'm sure it's not an NRWT issue bug a problem with Qt specific the crash logging code in WTR. One know limitation is that it's only works for crashes in the web process. I will take a look how could it be improved.
Balazs Kelemen
Comment 6 2011-10-21 09:04:39 PDT
I tried it locally with a random crash in the web process and the crash logs were ok. Could you point to a particular build at the bot where crash log was missing?
Csaba Osztrogonác
Comment 7 2012-06-21 04:47:06 PDT
It isn't problem now, we get crash logs regularly. There are missing crash logs sometimes, but they can't be reproducible and I don't think if they are NRWT related.
Note You need to log in before you can comment on or make changes to this bug.