This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 2/3] skip_prolgoue (amd64)
- From: Yao Qi <yao at codesourcery dot com>
- To: Doug Evans <dje at google dot com>
- Cc: Pedro Alves <palves at redhat dot com>, Mark Kettenis <mark dot kettenis at xs4all dot nl>, gdb-patches <gdb-patches at sourceware dot org>
- Date: Thu, 5 Dec 2013 09:37:59 +0800
- Subject: Re: [PATCH 2/3] skip_prolgoue (amd64)
- Authentication-results: sourceware.org; auth=none
- References: <1385735051-27558-1-git-send-email-yao at codesourcery dot com> <1385735051-27558-3-git-send-email-yao at codesourcery dot com> <201311291436 dot rATEaZ5Z030292 at glazunov dot sibelius dot xs4all dot nl> <201311291605 dot rATG5XVb030184 at glazunov dot sibelius dot xs4all dot nl> <52994E79 dot 4000004 at codesourcery dot com> <5299B9D0 dot 2020304 at redhat dot com> <CADPb22REFRk5r5sb_TmfduDEbos4sooF6LP9GKq9fXQ+g0T6GQ at mail dot gmail dot com>
On 12/05/2013 01:54 AM, Doug Evans wrote:
The dcache and non-stop are basically incompatible, but we need both.
Agreed.
With any other thread still running the ground can be pulled out from
underneath my view of memory from a stopped thread (even when I'm in
the middle of viewing it - I can imagine a pretty-printer of a complex
object getting really confused for example).
It feels like there's diminishing returns and increasing costs the
farther we go to try to protect the user from this.
That is reasonable. In the long term, we'll switch to "running
all-stop on top of non-stop", users shouldn't get staled results
because they think they are in "all-stop" mode, although all-stop is
"simulated" by non-stop, which is invisible to users.
--
Yao (éå)