From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mukesh Rathor Subject: Re: about kdb for Xen Date: Fri, 27 Mar 2009 13:53:42 -0700 Message-ID: <49CD3CD6.8080309@oracle.com> References: <3411131.2044551237885265110.JavaMail.nabble@isper.nabble.com> <49C99634.3050202@oracle.com> <8c2dc7030903242025o7a661a2yc9fa32370e7709d8@mail.gmail.com> <49CC3EE1.5060807@oracle.com> <8c2dc7030903270351q17449595wecd280022336de3@mail.gmail.com> Reply-To: mukesh.rathor@oracle.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <8c2dc7030903270351q17449595wecd280022336de3@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Liu Jian Cc: xen-devel List-Id: xen-devel@lists.xenproject.org Liu Jian wrote: > On Fri, Mar 27, 2009 at 10:50 AM, Mukesh Rathor > wrote: >> I think I'm not following you. If you enter go first time, the system is >> crashing. You are hitting an assert (BUG()) in the hypervisor. The >> victim is accpting input as you are able to type the second "go" when >> it's says cmd not avail in crash state. >> >> After the crash, you can use dr, f, dw, etc... all those commands but >> not the "go" cmd. >> > > Yes, "df, f, dw" works well. But the second "go" not and it show as following: > > [1]xkdb> go > cmd not available in fatal/crashed state...... > > Of course, now target victim cannot accept any input. You are saying you don't get kdb prompt back now? > >> 1. what version of xen are you using? > > All the code is cloned from your branch as following: > > [root@localhost ~]hg clone http://xenbits.xensource.com/ext/debuggers.hg > > In the compile process as following, It show the version is "3.4-unstable" > >> 2. Are you compiling hyp with -DEBUG? > > I just compile xen by: > > [root@localhost xen>make kdb=y > > Do you mean I need other parameters? The problem is debug is turned on. kdb is not currently supported with debug on, as I had said before. Do > make kdb=y debug=n I also suggest frame_pointer=y to get reliable stacks. Mukesh