New issue
Advanced search Search tips

Issue 852598 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

gdb warnings when using gdb on linux

Project Member Reported by sky@chromium.org, Jun 13 2018

Issue description

gdb version  7.9-gg19
tip of tree'ish build
rodette.

The warnings I see are along the lines of:

Dwarf Error: wrong version in compilation unit header (is 0, should be 2, 3, or 4) [in module /usr/lib/debug/.build-id/ef/9474f02d7f7a3959b6dae0afe8e6acee1ac5ba.debug]

My args.gn are:

target_os = "chromeos"
is_component_build = true
is_debug = true
enable_nacl = false
use_goma = true
remove_webcore_debug_symbols = true
use_ozone=true
ozone_auto_platforms=false
ozone_platform_x11=true
ozone_platform="headless"

They don't seem to cause any harm. This likely started happening with the move to rodette, but I couldn't be sure of that.
 

Comment 1 by sky@chromium.org, Jun 13 2018

It's also worth noting that when I attach to a chrome process (debug build) I get a ton of log spew too:

warning: Could not find DWO CU obj/services/network/public/mojom/mojom_shared_cpp_sources/digitally_signed.mojom-shared.dwo(0xda69bf1e0a3ff6a6) referenced by CU at\
 offset 0x14bef5 [in module /secondary/builds/build1/src/out/Debug/./libblink_platform.so]

Comment 2 by tikuta@chromium.org, Jun 14 2018

> Dwarf Error: wrong version in compilation unit header (is 0, should be 2, 3, or 4) [in module /usr/lib/debug/.build-id/ef/9474f02d7f7a3959b6dae0afe8e6acee1ac5ba.debug]

I don't have any idea about this, but

> warning: Could not find DWO CU obj/services/network/public/mojom/mojom_shared_cpp_sources/digitally_signed.mojom-shared.dwo(0xda69bf1e0a3ff6a6) referenced by CU at\
 offset 0x14bef5 [in module /secondary/builds/build1/src/out/Debug/./libblink_platform.so]

Do you see this warning even if you configure gdb like below?
https://chromium.googlesource.com/chromium/src/+/master/docs/linux_debugging.md#Source-level-debug-with-fdebug_prefix_map

Comment 3 by thakis@chromium.org, Jun 14 2018

Like tikuta says, the dwo parts are new. He points out how to fix; "Proposal: Use -fdebug-prefix-map by default for goma on Linux build" on chromium-dev was the email thread.

I wonder doing the config fixup for that maybe also helps with the other warnings?

Sign in to add a comment