Bug 33654 - Need an automated way to get symbolicated crash dumps from Qt build bot
Summary: Need an automated way to get symbolicated crash dumps from Qt build bot
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
Keywords: Qt, QtTriaged
: 38498 (view as bug list)
Depends on:
Reported: 2010-01-13 23:59 PST by Eric Seidel (no email)
Modified: 2014-02-03 03:50 PST (History)
5 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Eric Seidel (no email) 2010-01-13 23:59:03 PST
Need an automated way to get symbolicated crash dumps from Qt build bot

Even a manual way would be good.  Right now I know of no way to symbolicate crash dumps like bug 33653
Comment 1 Csaba Osztrogonác 2010-05-06 06:15:05 PDT
*** Bug 38498 has been marked as a duplicate of this bug. ***
Comment 2 Csaba Osztrogonác 2010-05-06 06:32:23 PDT
>Can this be symbolized before uploading, please?  It would make these crashes
>much easier to diagnose.

It is possible, but unfortunately compiling and linking always with symbols is very expensive (CPU load, memory load, build time, binary size, etc.). Our buildbot hardware is so overloaded now, I'm afraid we can't do it now until we setup new buildbot hardwares. But we can make the possibility to get symbolicated crash dumps with a command line option and we will be able to enable it in the future.

On our buildbot master there are a 32 bit and 64 bit debug bot: http://www.sed.hu/webkit/qtbuildbot/waterfall

They provide more useable crash log now, eg: http://www.sed.hu/webkit/qtbuildbot/results/x86-32%20Linux%20Qt%20Debug/r58876%20%283172%29/plugins/inner-html-display-none-stderr.txt

Only name demangling and lineinfos are missing now. :)
AFAIK gdb can make them from core file and symbolicated objects.
Comment 3 Jocelyn Turcotte 2014-02-03 03:50:37 PST
=== Bulk closing of Qt bugs ===

If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it.

If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.