From: Tom de Vries <tdevries@suse.de>
To: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [PATCH][gdb/testsuite] Compile index-cache.c with -Wl,--build-id
Date: Fri, 21 Jun 2019 15:54:00 -0000 [thread overview]
Message-ID: <62bf83ef-0c18-12a8-bfb0-8f3f28fa84ba@suse.de> (raw)
In-Reply-To: <cf27c5eb-60c1-681b-1635-ff6653f91759@redhat.com>
On 21-06-19 17:47, Pedro Alves wrote:
> 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"?
The latter.
Thanks,
- Tom
next prev parent reply other threads:[~2019-06-21 15:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 15:27 Tom de Vries
2019-06-21 15:47 ` Pedro Alves
2019-06-21 15:53 ` Simon Marchi
2019-06-21 15:54 ` Tom de Vries [this message]
2019-06-21 16:32 ` Pedro Alves
2019-06-21 16:51 ` Tom de Vries
2019-06-21 16:51 ` Tom de Vries
2019-06-25 19:06 ` Testcase regression (gdb.base/index-cache.exp) on x86_64 (was: Re: [PATCH][gdb/testsuite] Compile index-cache.c with -Wl,--build-id) Sergio Durigan Junior
2019-06-26 3:55 ` [committed][gdb/testsuite] Add back missing debug for index-cache.exp Tom de Vries
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=62bf83ef-0c18-12a8-bfb0-8f3f28fa84ba@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=simon.marchi@polymtl.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox