From: Phil Muldoon <pmuldoon@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [patchv2] compile: Fix GNU-IFUNC funcs called from injected code
Date: Wed, 25 Feb 2015 08:20:00 -0000 [thread overview]
Message-ID: <54ED85CC.7030506@redhat.com> (raw)
In-Reply-To: <20150224200237.GA1746@host1.jankratochvil.net>
On 24/02/15 20:02, Jan Kratochvil wrote:
> Testcase cosmetic update.
>
> compile-gnu-ifunc2.patch
>
> 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.
>
> gdb/testsuite/ChangeLog
> 2015-02-24 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * gdb.compile/compile-ifunc.c: New file.
> * gdb.compile/compile-ifunc.exp: New file.
Thanks. This looks great other than the following nit:
> case mst_text_gnu_ifunc:
> - type = objfile_type (objfile)->nodebug_text_gnu_ifunc_symbol;
> + // nodebug_text_gnu_ifunc_symbol would cause:
> + // function return type cannot be function
Not sure if we allow // comments yet.
> + if (TYPE_GNU_IFUNC (SYMBOL_TYPE (sym)))
> + result = gnu_ifunc_resolve_addr (target_gdbarch (), result);
Is this guaranteed to return a value to result (or an exception)?
Cheers
Phil
next prev parent reply other threads:[~2015-02-25 8:20 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 [this message]
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
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=54ED85CC.7030506@redhat.com \
--to=pmuldoon@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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