From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brendan Cully Subject: Re: help on debugging kernel module in Xen Date: Fri, 12 Jan 2007 15:21:16 -0800 Message-ID: <20070112232116.GH4982@ventoux.cs.ubc.ca> References: <4d616cca0701121041n62b8ad05k7996ffe125c43043@mail.gmail.com> <20070112192049.GA4982@ventoux.cs.ubc.ca> <4d616cca0701121225p1018056ar24541c3a27c57518@mail.gmail.com> <20070112205358.GC4982@ventoux.cs.ubc.ca> <4d616cca0701121307p67b8235bxb16689093b791976@mail.gmail.com> <4d616cca0701121310u7d26b2e5wf874699ac9dedeca@mail.gmail.com> <20070112212645.GE4982@ventoux.cs.ubc.ca> <4d616cca0701121332p5787be2erc1a003d4e6e4e55c@mail.gmail.com> <20070112214118.GF4982@ventoux.cs.ubc.ca> <4d616cca0701121504l6f3ca0fayd1b4e48f0531dc40@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4d616cca0701121504l6f3ca0fayd1b4e48f0531dc40@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: Lily Huang Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Friday, 12 January 2007 at 18:04, Lily Huang wrote: > That's a great point. I just disabled the "Detect Soft Lockup" option in the > "kernel hacking" group. Now the soft lockup disappeared and I can debug > kernel now. > > Next, I tried to debug kernel module in domU. New problem occurs. > > After I set "br xxx(function in a loaded kernel module" and then "cont", I > worked in the domu to activate the breakpoint. > > Unfortunately, I found domU immediately print error messages: > > /**********************************************************/ > Message from syslogd@normal at Fri Jan 12 17:54:41 2007 ... > normal kernel: int3: 0000 [#1] > <----------------------------------------------------- seems to be a problem > > Message from syslogd@normal at Fri Jan 12 17:54:41 2007 ... > normal kernel: SMP > > Message from syslogd@normal at Fri Jan 12 17:54:41 2007 ... > normal kernel: CPU: 0 > > Message from syslogd@normal at Fri Jan 12 17:54:41 2007 ... > normal kernel: EIP is at nfs3_proc_readdir+0xd/0x100 [nfs] > > Message from syslogd@normal at Fri Jan 12 17:54:41 2007 ... > normal kernel: eax: daa0c740 ebx: 00001000 ecx: c1353aa0 edx: db25cd14 > > Message from syslogd@normal at Fri Jan 12 17:54:41 2007 ... > normal kernel: esi: df02ced0 edi: daa0885c ebp: da9c7d34 esp: da9c7c4c > > Message from syslogd@normal at Fri Jan 12 17:54:41 2007 ... > normal kernel: ds: 007b es: 007b ss: 0069 > > Message from syslogd@normal at Fri Jan 12 17:54:41 2007 ... > normal kernel: Process ls (pid: 1670, threadinfo=da9c6000 task=c05d7070) > /**********************************************************/ > > Looks like "int 3" triggered kernel error. Why just for kernel module > debugging? I'm afraid you're beyond my knowledge at this point.