Include glibc debug files for standalone toolchain |
|||||||
Issue descriptionThis bug causes glibc to be included in the toolchain: https://bugs.chromium.org/p/chromium/issues/detail?id=755453 Can we include the debug files by default too?
,
Sep 25 2017
Do you mean the debug file of the toolchains?
,
Sep 25 2017
debug file for glibc
Standalone glibc has the .debug files
gs://chromeos-prebuilt/host/amd64/amd64-host/chroot-${snapshot}/packages/cross-${arch}-cros-linux-${abi}/glibc-${glibc_version}.tbz2
e.g. usr/lib/debug/.build-id/00/1ca5db08dad4610503fed5f63cceba6467405d
These are missing from the toolchain, so we cannot get debug symbols.
,
Sep 25 2017
that issue isn't related ... i'm assuming you mean issue 755693 i don't think .debug files should be bundled by default. the tarballs are already large enough. but that leaves the question of how we want to support this.
,
Sep 25 2017
Oops yes, I meant issue 755693 . If we don't want to include debug files I'm with with just closing this issue. We can just get them from the standone glibc.
,
Sep 25 2017
i understand that the binpkgs have the debug files. i don't think that's relevant to this discussion. you might have just noticed the C lib aspect, but there are many packages we ship in the standalone toolchain. we should have a coherent solution to all of them.
,
Dec 26 2017
,
Jan 2 2018
[It appears that a bunch of old cros issues bulk-added the "Infra" component recently, but they should probably be "Infra>Client>ChromeOS".]
,
Jan 4 2018
,
Feb 5 2018
,
Oct 24
,
Nov 13
Closing as won't fix. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by llozano@chromium.org
, Sep 25 2017Owner: yunlian@chromium.org
Status: Assigned (was: Untriaged)