missing line number in crash report |
||||||||
Issue descriptioncrash report for amd64 boards does not have line numbers. 0x00007f26e748edfd (libc-2.23.so + 0x000c3dfd ) __nanosleep_nocancel 0x00007f26e74ba937 (libc-2.23.so -usleep.c:32 ) usleep 0x00007f26ea220c09 (chrome + 0x0165bc09 ) ui::DrmDeviceHandle::Initialize(base::FilePath const&, base::FilePath const&) 0x00007f26ea221f40 (chrome + 0x0165cf40 ) ui::DrmDisplayHostManager::DrmDisplayHostManager(ui::GpuThreadAdapter*, ui::DeviceManager*, ui::InputControllerEvdev*) 0x00007f26ea22fc6d (chrome + 0x0166ac6d ) ui::(anonymous namespace)::OzonePlatformGbm::InitializeUI(ui::OzonePlatform::InitParams const&) 0x00007f26ea1efe87 (chrome + 0x0162ae87 ) ui::OzonePlatform::InitializeForUI() 0x00007f26ed1a03bd (chrome + 0x045db3bd ) aura::Env::Init() 0x00007f26ed1a0352 (chrome + 0x045db352 ) aura::Env::CreateInstance(aura::Env::Mode) 0x00007f26ea59a100 (chrome + 0x019d5100 ) content::BrowserMainLoop::InitializeToolkit() 0x00007f26ea59ab24 (chrome + 0x019d5b24 ) content::BrowserMainRunnerImpl::Initialize(content::MainFunctionParams const&) 0x00007f26ea593c13 (chrome + 0x019cec13 ) content::BrowserMain(content::MainFunctionParams const&) 0x00007f26eba5b293 (chrome + 0x02e96293 ) content::ContentMainRunnerImpl::Run() 0x00007f26eba84e2f (chrome + 0x02ebfe2f ) service_manager::Main(service_manager::MainParams const&) 0x00007f26eba5a1c0 (chrome + 0x02e951c0 ) content::ContentMain(content::ContentMainParams const&) 0x00007f26e9f7ebdb (chrome + 0x013b9bdb ) ChromeMain 0x00007f26e73eb815 (libc-2.23.so -libc-start.c:289 ) __libc_start_main 0x00007f26e9f7ea48 (chrome + 0x013b9a48 ) _start
,
Jul 14 2017
We enabled debug fission on amd64 in this CL https://chromium-review.googlesource.com/c/457302/ But we did not collect the .dwp file for it. As a result, we are missing part of debug information on R60 builds. The TOT fix was landed as https://chromium-review.googlesource.com/c/556070/ The risk to land this CL is minimum. It does not change any code/(debug symbols). It only adds the missing debug information. Without this CL, we hit some problems in #1. And we may hit more debug information related problems.
,
Jul 14 2017
,
Jul 14 2017
Please add OS tags...
,
Jul 17 2017
,
Jul 17 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/c75620024dfab4c7b977f2a8d20760e4c3b913cf commit c75620024dfab4c7b977f2a8d20760e4c3b913cf Author: Yunlian Jiang <yunlian@google.com> Date: Mon Jul 17 16:43:10 2017 chromeos-chrome: generate .dwp file for amd64 We enabled debug fission for amd64, and we need to create .dwp for then. BUG= chromium:743078 TEST=cbuild falco-release, the .dwp file is generated. Change-Id: I64f20cd54cf5d4e7ac62fd49aa5a2d4b45f14a2f Previous-Reviewed-on: https://chromium-review.googlesource.com/540105 (cherry picked from commit 266c809f2a574e575a2173c2bb78a983e10e431f) Reviewed-on: https://chromium-review.googlesource.com/570737 Reviewed-by: Josafat Garcia <josafat@chromium.org> Reviewed-by: Luis Lozano <llozano@chromium.org> Commit-Queue: Yunlian Jiang <yunlian@chromium.org> Tested-by: Yunlian Jiang <yunlian@chromium.org> Trybot-Ready: Yunlian Jiang <yunlian@chromium.org> [modify] https://crrev.com/c75620024dfab4c7b977f2a8d20760e4c3b913cf/chromeos-base/chromeos-chrome/chromeos-chrome-9999.ebuild
,
Jul 21 2017
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 21 2017
,
Jul 21 2017
,
Aug 3 2017
Closing. Please reopen it if its not fixed. Thanks! |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by sheriffbot@chromium.org
, Jul 14 2017