This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC] MI notification on register changes


>>>>> "Yao" == Yao Qi <yao@codesourcery.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

Yao> Yes.

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:

    http://sourceware.org/bugzilla/show_bug.cgi?id=7574

... which seems apropos.  It seems that the best thing is a generic
"target changed" notification for the reasons mentioned there.

Tom


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]