Re: about kdb for Xen

[Mukesh Rathor <mukesh.rathor@oracle.com>]

Liu Jian wrote:
> On Fri, Mar 27, 2009 at 10:50 AM, Mukesh Rathor
> <mukesh.rathor@oracle.com> 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