WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] help on debugging kernel module in Xen

To: ushuanglily@xxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] help on debugging kernel module in Xen
From: "Lily Huang" <ushuanglily@xxxxxxxxx>
Date: Fri, 12 Jan 2007 16:32:51 -0500
Delivery-date: Fri, 12 Jan 2007 13:32:25 -0800
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=ugE1X3MK10u68CSLLtRp5XxJhZx+Z7ybleUIJY8pWjrN/hL3tD4Y4Hdx6Z6vkzquhqrmxpIK+b3+oQJoPEfUtbfe0eSuyVsWEIGLCl6sO9Wujw0y9g7NCRa3T/mj7M75arWxrRz/TReFPAlfq3bMG6UioGz4FCxE+8RO3H3Ykxo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070112212645.GE4982@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4d616cca0701121041n62b8ad05k7996ffe125c43043@xxxxxxxxxxxxxx> <20070112192049.GA4982@xxxxxxxxxxxxxxxxx> <4d616cca0701121225p1018056ar24541c3a27c57518@xxxxxxxxxxxxxx> <20070112205358.GC4982@xxxxxxxxxxxxxxxxx> <4d616cca0701121307p67b8235bxb16689093b791976@xxxxxxxxxxxxxx> <4d616cca0701121310u7d26b2e5wf874699ac9dedeca@xxxxxxxxxxxxxx> <20070112212645.GE4982@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Brendan,

You are right. After I lift the breakpoint a little bit (to sys_open), the breakpoint works.

But now the domU kept complaining after I did "target remote 127.0.0.1:9999 " and then "br sys_open":

/************************************************?
BUG: soft lockup detected on CPU#0!

Pid: 0, comm:              swapper
EIP: 0061:[<c01013a7>] CPU: 0
EIP is at 0xc01013a7
 EFLAGS: 00000346    Not tainted  (2.6.16.33-xenU #12)
EAX: 00000000 EBX: 00000001 ECX: 00000000 EDX: 00000000
ESI: 00000001 EDI: c0354000 EBP: c0355f84 DS: 007b ES: 007b
CR0: 8005003b CR2: b7f77000 CR3: 1d633000 CR4: 00000640
 [<c0105bb3>] show_trace+0x13/0x20
 [<c0103390>] show_regs+0x190/0x1e0
 [<c013cf48>] softlockup_tick+0x88/0xa0
 [<c0126d45>] do_timer+0x215/0x440
 [<c010858c>] timer_interrupt+0x1bc/0x6a0
 [<c013d09f>] handle_IRQ_event+0x3f/0xd0
 [<c013d1be>] __do_IRQ+0x8e/0xf0
 [<c0106efd>] do_IRQ+0x1d/0x30
 [<c025d2d1>] evtchn_do_upcall+0xa1/0xe0
 [<c0105309>] hypervisor_callback+0x3d/0x48
 [<c01039df>] xen_idle+0x2f/0x60
 [<c0103a82>] cpu_idle+0x72/0xc0
 [<c0102035>] rest_init+0x35/0x40
 [<c035656a>] start_kernel+0x2ea/0x3a0
 [<c010006f>] 0xc010006f

/********************************************************/

What's wrong? Looks like I am really doomed to run into so many weird problems. :(

lily

On 1/12/07, Brendan Cully < brendan@xxxxxxxxx> wrote:
On Friday, 12 January 2007 at 16:10, Lily Huang wrote:
> Oh. I found that gdbserver printed out some error messages:
>
> unsupported xc_ptrace request PTRACE_SETFPXREGS
> unsupported xc_ptrace request PTRACE_SETFPREGS
>
> Are they the reason why the breakpoint does not work?

no, those are fairly harmless.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel