From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH master + 11][gdb/symtab] Fix zero address complaint for shlib
Date: Mon, 2 Aug 2021 09:09:24 -0400 [thread overview]
Message-ID: <86940b5e-76ba-fe28-eff1-2e3af832af70@polymtl.ca> (raw)
In-Reply-To: <31b389e1-fbfc-cdfa-14dd-5a4a99167430@suse.de>
Where it says:
> +# The .c files use __attribute__.
> +if [get_compiler_info] {
> + return -1
> +}
The .c files don't seem to use __attribute__.
I'm also wondering why we use this for these tests:
> +if !$gcc_compiled {
> + verbose "Skipping $gdb_test_file_name."
> + return 0
> +}
The test runs fine with CC_FOR_TARGET=clang, for example (with the trivial
fix to make main return int).
Simon
next prev parent reply other threads:[~2021-08-02 13:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 21:23 Tom de Vries
2021-07-30 1:25 ` Simon Marchi via Gdb-patches
2021-07-30 1:48 ` Simon Marchi via Gdb-patches
2021-07-30 15:25 ` Tom de Vries
2021-07-30 17:50 ` Simon Marchi via Gdb-patches
2021-08-01 17:59 ` Tom de Vries
2021-08-02 13:09 ` Simon Marchi via Gdb-patches [this message]
2021-08-06 14:43 ` Tom de Vries via Gdb-patches
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=86940b5e-76ba-fe28-eff1-2e3af832af70@polymtl.ca \
--to=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=tdevries@suse.de \
/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