New issue
Advanced search Search tips

Issue 857219 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Build-Toolchain



Sign in to add a comment

cros_install_debug_syms doesn't seem to get right debug symbols for chrome

Project Member Reported by cmtm@chromium.org, Jun 27 2018

Issue description

OS: gLinux

What steps will reproduce the problem?
(1) run "cros_install_debug_syms --board=caroline-arcnext --all"
output:
13:42:43: INFO: RunCommand: sudo -- /mnt/host/source/chromite/bin/cros_install_debug_syms '--board=caroline-arcnext' --all
13:42:44: INFO: RunCommand: /mnt/host/source/.cache/common/gsutil_4.30.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cat gs://chromeos-prebuilt/board/amd64-generic/paladin-R69-10807.0.0-rc1/packages/Packages
13:42:46: INFO: RunCommand: /mnt/host/source/.cache/common/gsutil_4.30.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cat gs://chromeos-prebuilt/board/caroline-arcnext/paladin-R69-10807.0.0-rc1/packages/Packages
13:42:47: INFO: RunCommand: /mnt/host/source/.cache/common/gsutil_4.30.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cat gs://chromeos-prebuilt/board/caroline/chrome-R69-10796.0.0-rc2/packages/Packages

(2) run "gdb-caroline-arcnext  --remote=cmtm-crbook --attach browser"
output:
[...]
14:11:53: INFO: 
/opt/google/chrome/chrome is stripped and /build/caroline-arcnext/usr/lib/debug/opt/google/chrome/chrome.debug does not exist on your local machine.
  The debug symbols for that package may not be installed.  To install the debug
 symbols for chromeos-base/chromeos-chrome-0
 only, run:

   cros_install_debug_syms --board=caroline-arcnext chromeos-base/chromeos-chrome-0


To install the debug symbols for all available packages, run:

   cros_install_debug_syms --board=caroline-arcnext --all
[...]

I can't access any of the debug symbols from within gdb


What is the expected result?
I should be able to see debug symbols from within gdb

What happens instead?
I don't see the debug symbols. I also think the prompt to run cros_intall_debug_syms after having already installed everything is erroneous.
 

Comment 1 by vapier@chromium.org, Jun 27 2018

Components: Infra>Client>ChromeOS>Build
Labels: -OS-Linux
Summary: cros_install_debug_syms doesn't seem to get right debug symbols for chrome (was: cros_install_debug_syms doesn't seem to get right debug symbols)
off the top of my head, we might treat Chrome special because its debug symbols tend to be much larger than anything else

Comment 2 by cmtm@chromium.org, Jun 27 2018

I tried just doing "cros_install_debug_syms --board=caroline-arcnext chromeos-base/chromeos-chrome-0" after, but I got a message saying "nothing to do, exit". If I remember correctly, I didn't have an issue debugging chrome the last time I used the "--all" option.
cros_install_debug_syms is used to generate debug symbols from the .debug file, if you want to debug chrome via gdb, there is no need to run this command.

Did you build chrome locally? The debug file will be installed to the right location after running USE="????" emerge-caroline-arcnext chromeos-chrome


Owner: yunlian@chromium.org
Status: Assigned (was: Untriaged)

Comment 5 by vapier@chromium.org, Jun 28 2018

i think you're thinking of cros_generate_breakpad_symbols.  cros_install_debug_syms is for fetching .debug files for already installed packages.

Comment 6 by cmtm@chromium.org, Jun 28 2018

I didn't build chrome locally. I ran "gdb-caroline-arcnext  --remote=cmtm-crbook --attach browser", and it told me to run that command to install debug symbols.
Could you please check that there are debug files under /build/caroline-arcnext/usr/lib/debug/opt/google/chrome/ ?

Comment 8 by cmtm@chromium.org, Jun 29 2018

The only file under the path /build/caroline-arcnext/usr/lib/debug/opt/google/chrome/ is "pepper/libpepflashplayer.so.debug"
There is something wrong here. I run the same command line and I got the chrome.debug some some other debug files.

Owner: ----
remove myself from the bug, I suspect this is build related.

Sign in to add a comment