Bug 182953

Summary: [WTR][GTK] crash log backtrace doesn't show symbol names for DatabaseProcess and NetworkProcess
Product: WebKit Reporter: Fujii Hironori <fujii.hironori>
Component: WebKitGTKAssignee: Fujii Hironori <fujii.hironori>
Status: RESOLVED FIXED    
Severity: Normal CC: bugs-noreply, cgarcia, commit-queue, ews-watchlist, glenn
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch
fujii.hironori: review-, fujii.hironori: commit-queue-
Patch
none
Archive of layout-test-results from ews205 for win-future none

Fujii Hironori
Reported 2018-02-19 20:45:14 PST
[WTR][GTK] crash log backtrace doesn't show symbol names for DatabaseProcess and WebKitNetworkProcess
Attachments
Patch (2.80 KB, patch)
2018-02-19 20:48 PST, Fujii Hironori
fujii.hironori: review-
fujii.hironori: commit-queue-
Patch (2.79 KB, patch)
2018-02-19 20:55 PST, Fujii Hironori
no flags
Archive of layout-test-results from ews205 for win-future (11.50 MB, application/zip)
2018-02-19 22:48 PST, EWS Watchlist
no flags
Fujii Hironori
Comment 1 2018-02-19 20:48:43 PST
Fujii Hironori
Comment 2 2018-02-19 20:55:38 PST
EWS Watchlist
Comment 3 2018-02-19 22:48:41 PST
Comment on attachment 334236 [details] Patch Attachment 334236 [details] did not pass win-ews (win): Output: http://webkit-queues.webkit.org/results/6584460 New failing tests: http/tests/preload/onerror_event.html
EWS Watchlist
Comment 4 2018-02-19 22:48:52 PST
Created attachment 334243 [details] Archive of layout-test-results from ews205 for win-future The attached test failures were seen while running run-webkit-tests on the win-ews. Bot: ews205 Port: win-future Platform: CYGWIN_NT-6.1-2.9.0-0.318-5-3-x86_64-64bit
WebKit Commit Bot
Comment 5 2018-02-19 23:08:05 PST
Comment on attachment 334236 [details] Patch Clearing flags on attachment: 334236 Committed r228731: <https://trac.webkit.org/changeset/228731>
WebKit Commit Bot
Comment 6 2018-02-19 23:08:07 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.