This is the mail archive of the
mailing list for the GDB project.
Re: [PATCH 4/4] compile: New 'compile print'
- From: Phil Muldoon <pmuldoon at redhat dot com>
- To: Eli Zaretskii <eliz at gnu dot org>, Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 27 Mar 2015 07:56:08 +0000
- Subject: Re: [PATCH 4/4] compile: New 'compile print'
- Authentication-results: sourceware.org; auth=none
- References: <20150326205727 dot 28223 dot 54648 dot stgit at host1 dot jankratochvil dot net> <20150326205752 dot 28223 dot 24230 dot stgit at host1 dot jankratochvil dot net> <83iodmnc18 dot fsf at gnu dot org> <20150327073333 dot GA28529 at host1 dot jankratochvil dot net> <83d23unazo dot fsf at gnu dot org>
On 27/03/15 07:41, Eli Zaretskii wrote:
>> Date: Fri, 27 Mar 2015 08:33:33 +0100
>> From: Jan Kratochvil <firstname.lastname@example.org>
>> Cc: email@example.com, firstname.lastname@example.org
>> On Fri, 27 Mar 2015 08:18:43 +0100, Eli Zaretskii wrote:
>>> I suggest a different name for this command. Unfortunately, "eval" is
>>> already taken, but perhaps "parse" or "parse-eval"? Or maybe a new
>>> switch to "print"? "compile print" sounds awkward and unintuitive to
>> FYI there is already "compile code" and "compile file".
> Yes, I know. But this command is different AFAIU: it doesn't compile
> any code at all. So prefixing it with "compile" doesn't sound right
> to me.
It does. It repackages the expression typed by the user into compilable form (with a scope, various bits of stack mapping, address translation, etc), send it to the compiler plugin that compiles it. GDB then runs the code in the inferior and captures the evaluated output and type and prints it.