This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH][gdb/testsuite] Compile index-cache.c with -Wl,--build-id
- From: Pedro Alves <palves at redhat dot com>
- To: Tom de Vries <tdevries at suse dot de>, gdb-patches at sourceware dot org
- Cc: Simon Marchi <simon dot marchi at polymtl dot ca>
- Date: Fri, 21 Jun 2019 16:47:35 +0100
- Subject: Re: [PATCH][gdb/testsuite] Compile index-cache.c with -Wl,--build-id
- References: <20190621152742.GA20230@delia>
On 6/21/19 4:27 PM, Tom de Vries wrote:
> Hi,
>
> When building gdb using a combined gcc/binutils-gdb build and running
> gdb.base/index-cache.exp we get:
> ...
> FAIL: gdb.base/index-cache.exp: test_cache_enabled_miss: at least one file was created
> FAIL: gdb.base/index-cache.exp: test_cache_enabled_miss: couldn't get executable build id
> FAIL: gdb.base/index-cache.exp: test_cache_enabled_hit: check index-cache stats
> ...
>
> With "set debug index-cache on" we get:
> ...
> (gdb) file index-cache
> Reading symbols from index-cache...
> index cache: objfile index-cache has no build id
> ...
>
> The problem is that the vanilla toolchain does not add a build-id, which is
> required for the index-cache functionality.
What is "vanilla" here? A non-combined gcc/build-gdb build?
Or is "combined gcc/build-gdb build" irrelevant here, and
"vanilla" means "no-distro-patches build"? Was the testcase
written on a system with a compiler that defaults to --build-id ?
Thanks,
Pedro Alves