google-chrome-stable debuginfo or src.rpm package

[Tomasz Kłoczko]

Hi,

I need the access to debuginfo official google-chrome-stable package to try diagnose some issue. Seems official package is not provided with debuginfo subpackage so I would be happy to download src.rpm package generated during build or if official package is only packaging binaries generated other way I would be glad have look on details how exactly source tree is configured and build.
Can someone point on those resources?

Tomasz
-- 

Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH

[Lei Zhang]

There are no debugging symbols publicly available for Google Chrome on
Linux. The tracking bug for this issue is https://crbug.com/42985 .
One workaround is to see if you can reproduce your issue with
Chromium, which may have a debugging symbols package available.

> --
> --
> 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/CABB28CzfQwZU5F_xHPO8JYohLOVuJYM3bQBGvc6qgnhLSDQdWw%40mail.gmail.com.

[Tomasz Kłoczko]

On 7 July 2017 at 17:36, Lei Zhang <the...@chromium.org> wrote:

There are no debugging symbols publicly available for Google Chrome on
Linux. The tracking bug for this issue is https://crbug.com/42985 .
One workaround is to see if you can reproduce your issue with
Chromium, which may have a debugging symbols package available.

OK, so what about package build procedure? There are somewhere details about this?

[Lei Zhang]

On Fri, Jul 7, 2017 at 9:41 AM, Tomasz Kłoczko <kloczko...@gmail.com> wrote:
> OK, so what about package build procedure? There are somewhere details about
> this?

It's somewhat pointless to provide a src.rpm for Google Chrome, as one
would need the non-open parts of Chrome to do the build. The actual
build procedure is relatively straightforward, and only slightly
different from developer builds of Chromium. See the "Official Chrome
build" section on
https://www.chromium.org/developers/gn-build-configuration .

[Tomasz Kłoczko]

I'm not asking about exactly the src.rpm but about details of build procedure to build the same binaries with debug info.

About what kind of non-open source parts you are talking about?
URL which you posted does not contain details about google-chrome-stable build procedure. It contains general documentation of the build framework which seems is used only in chrome.

[Lei Zhang]

On Fri, Jul 7, 2017 at 10:09 AM, Tomasz Kłoczko

<kloczko...@gmail.com> wrote:
> On 7 July 2017 at 17:55, Lei Zhang <the...@chromium.org> wrote:
>>
>> On Fri, Jul 7, 2017 at 9:41 AM, Tomasz Kłoczko <kloczko...@gmail.com>
>> wrote:
>> > OK, so what about package build procedure? There are somewhere details
>> > about
>> > this?
>>
>> It's somewhat pointless to provide a src.rpm for Google Chrome, as one
>> would need the non-open parts of Chrome to do the build. The actual
>> build procedure is relatively straightforward, and only slightly
>> different from developer builds of Chromium. See the "Official Chrome
>> build" section on
>> https://www.chromium.org/developers/gn-build-configuration .
>
>
> I'm not asking about exactly the src.rpm but about details of build
> procedure to build the same binaries with debug info.
> About what kind of non-open source parts you are talking about?
> URL which you posted does not contain details about google-chrome-stable
> build procedure. It contains general documentation of the build framework
> which seems is used only in chrome.

Have you ever wondered about the differences between Google Chrome and
Chromium? Here is one webpage that attempts to explain some of the
differences:

https://chromium.googlesource.com/chromium/src/+/master/docs/chromium_browser_vs_google_chrome.md

If you care about building a Google Chrome branded binary, then the
page I linked to contains the procedure to set up a build
configuration to do just that. See also the assumptions at the top of
the page. General documentation on how to set up a build / actually do
the build are on the same website. If you are curious, please read the
developer documentation on https://www.chromium.org/developers/ .

I should also note that our build tools may not be 100% deterministic,
so even someone who can build a Google Chrome binary may not be able
to build the exact binary that is shipped to users.

As for building the RPM itself, Google Chrome RPM builds are not built
from src.rpm files. Instead, we have a set of scripts in
chrome/installer/linux to generate the packages. Just going from
memory, I think the "stable" build target with a Chrome branded build
config will build the stable channel .deb and .rpm.

[Tomasz Kłoczko]

On 7 July 2017 at 18:26, Lei Zhang <the...@chromium.org> wrote:

Have you ever wondered about the differences between Google Chrome and
Chromium?

Please. If you are not going to provide answer on my question just please do not reply.
I'm NOT asking about chromium. My question is about official chrome binaries provided by google.

Here is one webpage that attempts to explain some of the
differences:

https://chromium.googlesource.com/chromium/src/+/master/docs/chromium_browser_vs_google_chrome.md

If you care about building a Google Chrome branded binary, then the
page I linked to contains the procedure to set up a build
configuration to do just that. See also the assumptions at the top of
the page. General documentation on how to set up a build / actually do
the build are on the same website. If you are curious, please read the
developer documentation on https://www.chromium.org/developers/ .

Please stop sending random URLs not related to my question.
Are you person responsible for building those binaries? If not do you know who it is?

I should also note that our build tools may not be 100% deterministic,

Why are you pointing that chrome binaries build using exact procedure are not 100% deterministic?

It is really way easier just do not reply on someone question if you don't know the answer. Isn't it?

Tomasz

[Lei Zhang]

On Fri, Jul 7, 2017 at 10:35 AM, Tomasz Kłoczko
<kloczko...@gmail.com> wrote:
> On 7 July 2017 at 18:26, Lei Zhang <the...@chromium.org> wrote:
>>
>> Have you ever wondered about the differences between Google Chrome and
>> Chromium?
>
>
> Please. If you are not going to provide answer on my question just please do
> not reply.
> I'm NOT asking about chromium. My question is about official chrome binaries
> provided by google.

Well, you asked about "details of build procedure" and "what kind of
non-open source parts you are talking about" so I am replying to your
questions. Parts of the answers are not simple things that can be
easily explained in emails, so I linked to the documentation that
explains in further detail. They are related to your question, but if
you cannot accept that, then I cannot help you further.

The most straight forward answer I can give is: You cannot build
Google Chrome binaries because you do not have access to all of the
Google Chrome source code.

[Ryan Sleevi]

Hi Tomasz,

It may be worth stopping by https://www.chromium.org/conduct , as Lei
is trying to help you and answer your questions, and is one of the
people best suited for it, having contributed significantly to the
Chrome on Linux build system and infrastructure.

To try and recap your various answers, as perhaps it's not clear that
Lei has answered your questions:
- A src.rpm is not provided for Google Chrome, due to the non-public
sources. These differences are covered on the
https://chromium.googlesource.com/chromium/src/+/master/docs/chromium_browser_vs_google_chrome.md
page, and thus that serves to explain why that isn't provided.
- Similarly, debuginfo is not provided for this same reason.
- Even if a src.rpm was provided, it would not be sufficient to just
build from source to get the equivalent debuginfo from existing
crashes, due to the non-deterministic nature of the build system.
Thus, even if you did have a src.rpm that allowed you to build with
debuginfo, you would not be able to apply it to existing crashes - you
would need to reproduce these in your newly built binary.

Since you'd have to build a binary anyways, and since you cannot
access the sources for Google Chrome (as covered already), Lei
suggested you see if you can reproduce this in Chromium. As Chromium
is open-source, you would be able to build a package, along with the
debug information, and if you could reproduce the crash, this would
have all the information you need.

Hopefully this explains how Lei has been answering your questions
honestly, respectfully, and in good faith, and hopefully this provides
enough for you to diagnose the issues, since, as already covered, you
will not be able to do so for the official google-chrome RPM.

Cheers

[Tomasz Kłoczko]

Despitee those changes by add some non-OSS code still it ould be good to know at least things like how source code tree has been configured to repead te same settings on building chromium.

Tomasz

-- 

Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH