From mboxrd@z Thu Jan  1 00:00:00 1970
From: Emre Can Sezer <ecsezer@ncsu.edu>
Subject: Debugging Xen via serial console
Date: Wed, 28 Jan 2009 13:53:57 -0500
Message-ID: <4980A9C5.9040303@ncsu.edu>
References: <49677143.8060101@ncsu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <49677143.8060101@ncsu.edu>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Xen Devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

I'm trying to debug Xen remotely using serial port.  I followed the 
instructions on the following post made in this xen-devel list:
http://lists.xensource.com/archives/html/xen-devel/2007-12/msg00678.html

I was able to connect gdb but I ran into a problem where even after I 
clear all the breakpoints, execution traps into gdb with SIGTRAP at 
restore_all_xen().  This only happens if I set a breakpoint and then try 
to continue after hitting the break point.  If I simply connect gdb but 
continue without setting any breakpoints, everything is OK.

The post mentions some stability issues and I haven't seen any follow 
ups.  Is this still a viable debugging method?  Or is there some other 
method I should try?

Thanks in advance,

John