This is the mail archive of the
mailing list for the GDB project.
Re: [RFC] MI notification on register changes
- From: Tom Tromey <tromey at redhat dot com>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: <gdb-patches at sourceware dot org>
- Date: Fri, 02 Nov 2012 10:42:13 -0600
- Subject: Re: [RFC] MI notification on register changes
- References: <firstname.lastname@example.org> <email@example.com> <509398D8.firstname.lastname@example.org>
>>>>> "Yao" == Yao Qi <email@example.com> writes:
Tom> The register may be stored in memory, but it this case really ever
Tom> represented as lval_memory in gdb? I thought the reason for
We discussed this on irc a bit and I thought I'd email the list to keep
the thread up-to-date.
First, Yao sees that lval_memory on x86, but I don't see it on x86-64.
I wonder whether it is a bug elsewhere.
Second, Pedro pointed out this PR:
... which seems apropos. It seems that the best thing is a generic
"target changed" notification for the reasons mentioned there.