From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org
Cc: Phil Muldoon <pmuldoon@redhat.com>
Subject: Re: [patchv2] compile: Fix GNU-IFUNC funcs called from injected code
Date: Thu, 26 Feb 2015 15:49:00 -0000 [thread overview]
Message-ID: <54EF409C.9090102@redhat.com> (raw)
In-Reply-To: <20150224200237.GA1746@host1.jankratochvil.net>
On 02/24/2015 08:02 PM, Jan Kratochvil wrote:
>
> gdb/ChangeLog
> 2015-02-24 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * compile/compile-c-symbols.c (convert_one_symbol, convert_symbol_bmsym)
> (gcc_symbol_address): Call gnu_ifunc_resolve_addr.
Looks good to me too. OK.
I think we could probably avoid the extra infcall done
within gnu_ifunc_resolve_addr if we're going to be running
the generated code anyway, but it's not worth the effort
at this point.
> +if { [prepare_for_testing ${testfile}.exp "$testfile-debug" $srcfile] } {
> + return -1
> +}
> +
> +if ![runto_main] {
> + return -1
> +}
> +
Could you move these inside the prefix too, so that if they
fail for some reason, we get distinct test messages from
the nodebug case?
> +with_test_prefix "debug" {
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-02-26 15:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150224190720.GA32497@host1.jankratochvil.net>
2015-02-24 20:02 ` Jan Kratochvil
2015-02-25 8:20 ` Phil Muldoon
2015-02-25 17:29 ` Jan Kratochvil
2015-02-26 8:18 ` Joel Brobecker
2015-02-26 8:30 ` Jan Kratochvil
2015-02-26 9:34 ` Joel Brobecker
2015-02-26 10:54 ` Jan Kratochvil
2015-02-26 15:16 ` Joel Brobecker
2015-02-26 15:49 ` Pedro Alves [this message]
2015-02-26 16:43 ` [commit] " Jan Kratochvil
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=54EF409C.9090102@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=pmuldoon@redhat.com \
/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