From: Michael Snyder <msnyder@vmware.com>
To: "tromey@redhat.com" <tromey@redhat.com>
Cc: Marc Khouzam <marc.khouzam@ericsson.com>,
'Joel Brobecker' <brobecker@adacore.com>,
"'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>
Subject: Re: Another proposal for frontends and queries.
Date: Thu, 17 Sep 2009 00:16:00 -0000 [thread overview]
Message-ID: <4AB17FC0.2050003@vmware.com> (raw)
In-Reply-To: <m363biprql.fsf@fleche.redhat.com>
Tom Tromey wrote:
>>>>>> "Marc" == Marc Khouzam <marc.khouzam@ericsson.com> writes:
>
> Marc> Having a switch on a command turns out to be insufficient because
> Marc> there is not a 1-1 mapping between queries and commands. Currently
> Marc> PRecord will query before changing memory, but this will be triggered
> Marc> by any of:
> Marc> -var-assign a 8
> Marc> p a=8
> Marc> set var a=8
> Marc> and others.
>
> I am curious about something here. If you know the answers offhand, I'd
> appreciate it. Otherwise I guess I'll look into it at some later point.
>
> Does the record code also query when making an inferior function call
> from an expression? It seems like it ought to, as such a call might
> modify the inferior's state.
It will, because the set-up for the call will involve changing
the stack pointer register as well as the eip. The register
changes will get a prompt, even if nothing gets written to the stack
(memory).
> Also, if an expression does multiple assignments, are there multiple
> queries or just one? It seems like there should just be one.
At a guess, the first "no" will end it (because it will error out),
but you might have to say "yes" repeatedly. I haven't tried it.
next prev parent reply other threads:[~2009-09-17 0:16 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 2:38 Marc Khouzam
2009-09-14 6:45 ` Vladimir Prus
2009-09-14 13:07 ` Marc Khouzam
2009-09-14 14:09 ` Joel Brobecker
2009-09-14 14:28 ` Marc Khouzam
2009-09-14 14:48 ` Pedro Alves
2009-09-14 14:57 ` Marc Khouzam
2009-09-14 15:08 ` Joel Brobecker
2009-09-14 15:36 ` Marc Khouzam
2009-09-14 16:06 ` Joel Brobecker
2009-09-15 16:26 ` Joel Brobecker
2009-09-16 6:24 ` Hui Zhu
2009-09-16 12:38 ` Marc Khouzam
2009-09-16 13:06 ` Hui Zhu
2009-09-16 13:25 ` Pedro Alves
2009-09-16 13:46 ` Hui Zhu
2009-09-16 13:59 ` Marc Khouzam
2009-09-16 14:17 ` Hui Zhu
2009-09-16 14:26 ` Joel Brobecker
2009-09-16 14:34 ` Hui Zhu
2009-09-16 14:45 ` Pedro Alves
2009-09-16 14:43 ` Marc Khouzam
2009-09-16 18:03 ` Tom Tromey
2009-09-16 23:36 ` Hui Zhu
2009-09-16 23:40 ` Joel Brobecker
2009-09-16 17:12 ` Eli Zaretskii
2009-09-14 15:23 ` Joel Brobecker
2009-09-16 20:20 ` Tom Tromey
2009-09-16 20:35 ` Marc Khouzam
2009-09-17 0:17 ` Michael Snyder
2009-09-17 0:48 ` Marc Khouzam
2009-09-17 1:03 ` Joel Brobecker
2009-09-17 2:07 ` Marc Khouzam
2009-09-17 0:16 ` Michael Snyder [this message]
2009-09-16 20:43 ` Tom Tromey
2009-09-16 21:41 ` Joel Brobecker
2009-09-17 13:51 ` Marc Khouzam
2009-09-17 19:52 ` Tom Tromey
2009-09-18 4:59 ` Hui Zhu
2009-09-18 5:16 ` Michael Snyder
2009-09-18 9:31 ` Pedro Alves
2009-09-18 14:37 ` Joel Brobecker
2009-09-18 14:57 ` Marc Khouzam
2009-09-18 16:42 ` Tom Tromey
2009-09-22 0:46 ` Marc Khouzam
2009-09-22 22:49 ` [RFA/commit] s/nquery/query/ in record.c (was "Re: Another proposal for frontends and queries.") Joel Brobecker
2009-09-23 12:45 ` Marc Khouzam
2009-09-24 3:05 ` Hui Zhu
2009-09-24 17:59 ` Joel Brobecker
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=4AB17FC0.2050003@vmware.com \
--to=msnyder@vmware.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--cc=tromey@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