From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: pmuldoon@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH 4/4] compile: New 'compile print'
Date: Fri, 27 Mar 2015 10:11:00 -0000 [thread overview]
Message-ID: <20150327101117.GA3138@host1.jankratochvil.net> (raw)
In-Reply-To: <834mp6bw71.fsf@gnu.org>
On Fri, 27 Mar 2015 10:56:18 +0100, Eli Zaretskii wrote:
> Are you sure the last part (calling functions in the inferior) will
> work
Yes, as 'compile print' is almost the same as 'compile code' and for 'compile
code' it is already a part of the gdb.compile/ GDB testsuite.
> on all platforms? Won't it need some kind of import library on Windows?
I really have no idea(+interest+duties). Have you tried it?
> How does the GCC plugin know to resolve the address of the inferior's
> functions correctly?
compile_object_load() contains relocator for mst_text references.
Additionally convert_one_symbol()/convert_symbol_bmsym()/etc. provide symbol
addresses during compilation of the module. Some symbol types are resolved
that way, other symbols types the other way, it is partially interchangeable.
Jan
next prev parent reply other threads:[~2015-03-27 10:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 20:57 [PATCH 1/4] Code cleanup: Make parts of print_command_1 public Jan Kratochvil
2015-03-26 20:57 ` [PATCH 3/4] compile: Constify some parameters Jan Kratochvil
2015-04-06 17:28 ` obsolete: " Jan Kratochvil
2015-03-26 20:57 ` [PATCH 2/4] compile: Add new field scope_data Jan Kratochvil
2015-04-06 17:28 ` obsolete: " Jan Kratochvil
2015-03-26 20:58 ` [PATCH 4/4] compile: New 'compile print' Jan Kratochvil
2015-03-26 20:59 ` Jan Kratochvil
2015-03-27 7:18 ` Eli Zaretskii
2015-03-27 7:33 ` Jan Kratochvil
2015-03-27 7:41 ` Eli Zaretskii
2015-03-27 7:56 ` Phil Muldoon
2015-03-27 9:08 ` Eli Zaretskii
2015-03-27 9:10 ` Eli Zaretskii
2015-03-27 9:16 ` Jan Kratochvil
2015-03-27 9:56 ` Eli Zaretskii
2015-03-27 10:11 ` Jan Kratochvil [this message]
2015-03-27 10:20 ` Phil Muldoon
2015-03-27 13:09 ` Eli Zaretskii
2015-03-27 10:24 ` Jan Kratochvil
2015-03-27 13:12 ` Eli Zaretskii
2015-04-05 17:01 ` cancel: " Jan Kratochvil
2015-04-06 17:29 ` obsolete: " Jan Kratochvil
2015-03-27 20:06 ` [PATCH 1/4] v2: Code cleanup: Make parts of print_command_1 public Jan Kratochvil
2015-04-06 17:27 ` obsolete: " 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=20150327101117.GA3138@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).