Debug build of Chrome won't run

[Jeffrey Kardatzke]

I'm trying to make a debug build of Chrome to get the extra logging that goes with it. I've built Chrome hundreds of times before without problem using the following steps in the chroot:

gn gen out_$SDK_BOARD/Release --args="$GN_ARGS"

ninja -C out_${SDK_BOARD}/Release -j1000 chrome chrome_sandbox nacl_helper

deploy_chrome --build-dir=out_${SDK_BOARD}/Release --to=my_crbook

I then checked the args using:

gn args out_$SDK_BOARD/Release

and found that is_debug was set to false. So I changed it to true, then it complained about the is_official_build flag, so I changed that to false as well and then it built and deployed to the Chromebook just fine.

However, it's not starting up. If I look in /var/log/messages I can see it trying to start /opt/google/chrome and failing instantly each time. In /var/log/ui/ui.LATEST I see this:

/opt/google/chrome/chrome: error while loading shared libraries: libembedder.so: cannot open shared object file: No such file or directory

Weird...and if I put libembedder.so in /usr/lib that error goes away, but then another library error pops up.  It looks like everything is not being statically linked into the Chrome binary like it should be.

Anybody know how to fix this problem so I can get a debug build?  And I also tried blowing away the output directory and rebuilding it all again and the same problem occurred.

[Dirk Pranke]

It sounds like you're trying to do a static debug build of Chrome to deploy onto a Chromebook, is that right?

I don't know about ChromeOS, but at least as far as Linux goes, we don't really support static debug builds, so I wouldn't be surprised if you were hitting weird errors there from things not being statically linked. 

Maybe someone more knowledgeable about ChromeOS builds can chime in, or you might have luck on the chromiumos-dev list?

-- Dirk

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/2f863f43-c35e-4cd6-a1c3-3df3072db58f%40chromium.org.

[Jeffrey Kardatzke]

Yes this is for deployment to a Chromebook. I'll just try copying over all the .so files since this is expected, that shouldn't be too much trouble.

Jeff Kardatzke
Sent from my Android

[Sean]

This used to work as far as I remember.  I just tried it for the first time in a while and saw the same thing.

[Kyle]

When you change is_debug = true it changes the default for is_component_build to be true, so you've actually compiled a debug component build.

https://cs.chromium.org/chromium/src/build/config/BUILDCONFIG.gn?type=cs&q=%22is_component_build+%3D%22+file:.*%5C.gn&l=168

You can just add is_component_build=false to your GN args to get a static debug build.

Kyle

[Jeffrey Kardatzke]

Kyle, Thanks, that worked for creating a static binary...but now I have a new problem when Chrome tries to start up I get this error in the logs which leads to a crash in Chrome. Anybody know what's causing this?

[29628:29865:0620/112635.217392:VERBOSE1:drm_device_handle.cc(83)] Succeeded authenticating /dev/dri/card0 in 0 ms with 1 attempt(s)

device-enumerator: scan all dirs

  device-enumerator: scanning /sys/bus

  device-enumerator: scanning /sys/class

[29817:29817:0620/112635.365053:ERROR:gles2_cmd_decoder.cc(2525)] [GroupMarkerNotSet(crbug.com/242999)!:74850FBE]GL ERROR :GL_INVALID_FRAMEBUFFER_OP

ERATION : BackFramebuffer::Create: <- error from previous GL command

[29817:29817:0620/112635.381277:FATAL:gl_context.cc(278)] Check failed: error == GL_NO_ERROR || error == GL_CONTEXT_LOST_KHR. GL error was: 1286

#0 0x0000b27c54e2 <unknown>

---snip---

#34 0x0000ae7a3e4e <unknown>

#35 0x0000f05c08b8 __libc_start_main

Unexpected crash report id length

System crash_reporter failed to process crash report.

Report Id: 

[29628:29628:0620/112635.535542:ERROR:command_buffer_proxy_impl.cc(230)] Failed to send GpuChannelMsg_CreateCommandBuffer.

[29628:29628:0620/112635.535973:ERROR:context_provider_command_buffer.cc(262)] GpuChannelHost failed to create command buffer.

[29628:29811:0620/112635.569960:VERBOSE1:drm_device_handle.cc(83)] Succeeded authenticating /dev/dri/card1 in 0 ms with 1 attempt(s)

SYS_ioctl: VIDIOC_ENUM_FMT(2): fd=71, ret=-1, errno=22

SYS_ioctl: VIDIOC_ENUM_FMT(2): fd=71, ret=-1, errno=22

[29877:29877:0620/112635.884438:ERROR:generic_v4l2_device.cc(109)] SetDevicePollInterrupt(): write() failed: Bad file descriptor

[29877:29889:0620/112635.901987:ERROR:hardware_display_plane_atomic.cc(73)] Could not find property rotation

[29877:29889:0620/112635.902407:ERROR:hardware_display_plane_atomic.cc(141)] Unable to get plane properties.

[29877:29889:0620/112635.910428:ERROR:hardware_display_plane_atomic.cc(73)] Could not find property rotation

[29877:29889:0620/112635.910818:ERROR:hardware_display_plane_atomic.cc(141)] Unable to get plane properties.

[29628:29628:0620/112635.919875:VERBOSE1:signin_screen_handler.cc(677)] OnNetworkReady() call.

[29628:29628:0620/112635.919976:VERBOSE1:gaia_screen_handler.cc(244)] MaybePreloadAuthExtension

[29877:29889:0620/112635.921349:VERBOSE1:drm_device_manager.cc(54)] Could not initialize DRM device for /sys/devices/platform/vgem/drm/card0

[29628:29628:0620/112636.007697:VERBOSE1:arc_audio_bridge.cc(57)] HEADPHONE 0 MICROPHONE 0

[29628:29628:0620/112636.007810:VERBOSE1:arc_audio_bridge.cc(86)] Send switch state 0

[29628:29628:0620/112636.007868:VERBOSE1:instance_holder.h(67)] Instance for arc::mojom::AudioInstance::NotifySwitchState not available.

device-enumerator: scan all dirs

  device-enumerator: scanning /sys/bus

  device-enumerator: scanning /sys/class

[29628:29628:0620/112636.096916:VERBOSE1:drm_display_host_manager.cc(244)] Got display event ADD for /dev/dri/card1

[29628:29628:0620/112636.107121:VERBOSE1:drm_display_host_manager.cc(244)] Got display event ADD for /dev/dri/card0

[29877:29877:0620/112636.291631:ERROR:gles2_cmd_decoder.cc(2525)] [GroupMarkerNotSet(crbug.com/242999)!:744587C7]GL ERROR :GL_INVALID_FRAMEBUFFER_OPERATION : BackFramebuffer::Create: <- error from previous GL command

[29877:29877:0620/112636.306542:FATAL:gl_context.cc(278)] Check failed: error == GL_NO_ERROR || error == GL_CONTEXT_LOST_KHR. GL error was: 1286

#0 0x0000bc0e54e2 <unknown>

--

--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---

You received this message because you are subscribed to a topic in the Google Groups "Chromium-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/a/chromium.org/d/topic/chromium-dev/rsMKOZEJghM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to chromium-dev+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/b8825143-e9c7-420d-b087-711464fcb3df%40chromium.org.

--

Jeffrey Kardatzke

jkard...@google.com

Google, Inc.

[Jeffrey Kardatzke]

Apparently this error exists in release builds as well, but it just doesn't DCHECK so it's able to run....commenting out that DCHECK in gl_context.cc allows Chrome to run as a debug build.

[Hirokazu Honda]

An issue I previously filed would be helpful for you. (crbug.com/711618)

>>> chromium-dev...@chromium.org.

>>> To view this discussion on the web visit
>>> https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/b8825143-e9c7-420d-b087-711464fcb3df%40chromium.org.
>>
>>
>>
>>
>> --
>> Jeffrey Kardatzke
>> jkard...@google.com
>> Google, Inc.
>
>
>
>
> --
> Jeffrey Kardatzke
> jkard...@google.com
> Google, Inc.
>

> --
> --
> Chromium Developers mailing list: chromi...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-dev
> ---

> You received this message because you are subscribed to the Google Groups
> "Chromium-dev" group.

> To view this discussion on the web visit

> https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CA%2BddPcPy%3DQXU7RE7K9HeL-F6Hfzn59u%3DgVVSE_RvxS9rVcS7WA%40mail.gmail.com.

[drc...@chromium.org]

So I ran into this issue today too (is_debug = true and Chrome not starting because libembedder.so isn't on my M65 10281.0.0 Chrome OS). Do we always need to set is_component_build = false when using debug?  

On Monday, June 19, 2017 at 5:21:15 PM UTC-7, Jeffrey Kardatzke wrote:

[Christian Biesinger]

You should really ask ChromeOS questions on chromium-os-discuss or
chromium-os-dev, not here. For Chromium itself, debug builds work fine
as component builds.

Christian

> --
> --
> Chromium Developers mailing list: chromi...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-dev
> ---
> You received this message because you are subscribed to the Google Groups
> "Chromium-dev" group.
> To view this discussion on the web visit

> https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/d7d4cf70-4b73-49a0-b374-d08b2badfbba%40chromium.org.

[Yves Arrouye]

My bad, I will.