From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [xen-devel] [Patch 0/4] Xen stack trace printing improvements Date: Mon, 09 Sep 2013 04:09:43 -0700 Message-ID: References: <1376078158-13739-1-git-send-email-andrew.cooper3@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1376078158-13739-1-git-send-email-andrew.cooper3@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andrew Cooper , Xen-devel Cc: Tim Deegan , Jan Beulich List-Id: xen-devel@lists.xenproject.org On 09/08/2013 20:55, "Andrew Cooper" wrote: > This series consists of improvements to Xen's ability to print traces of its > own stack, and specifically for the stack overflow case to be able to use > frame pointers in a debug build. > > I have dev tested the series in debug and non-debug cases, with and without > memory guards, and I believe that all the stack traces look correct. However, > I would greatly appreciate a second opinion on the boundary conditions. > > The 4th patch is included for anyone wishing to easily test the series; It is > not intended for committing. > > Signed-off-by: Andrew Cooper > CC: Keir Fraser > CC: Jan Beulich > CC: Tim Deegan Acked-by: Keir Fraser