From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [xen-devel] [Patch 0/4] Xen stack trace printing improvements Date: Mon, 9 Sep 2013 13:28:27 +0100 Message-ID: <522DBEEB.90304@citrix.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Keir Fraser Cc: Tim Deegan , Jan Beulich , Xen-devel List-Id: xen-devel@lists.xenproject.org On 09/09/13 12:09, Keir Fraser wrote: > 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 > > Thanks for the ack, but I would like to hold off on committing this until I have fixed the bug for following frame pointers through exception frames. ~Andrew