Hi, I followed the instructions in tools/debugger/gdb/README to enable the xen debugging feature. But after that my system (a kernel module) works 10 times slower. Maybe the debugger slows down the running. What''s the right way to reverse and disable the debugger? I tried to disable the "Kernel hacking -> Compile the kernel with debug info [*]" option. But it does not help. Any ideas? Thanks, -l _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
"Lily Huang" <ushuanglily@gmail.com> writes:> Hi, > > I followed the instructions in tools/debugger/gdb/README to enable the xen > debugging feature. But after that my system (a kernel module) works 10 times > slower. Maybe the debugger slows down the running. > > What''s the right way to reverse and disable the debugger? I tried to disable > the "Kernel hacking -> Compile the kernel with debug info [*]" option. But it > does not help. Any ideas?Just terminate gdbserver-xen. If that doesn''t do it: What are your exact steps from `runs normally'' to `runs slowly''? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thanks a lot for your help! I already found the problem. My system is slowed down because of misconfiguration, nothing to do with the debugger. But another funny thing for me is that once I used ctrl+c to terminate gdbserver-xen, the dom0 will immediately reboot. My setting is as follows: 1. I ran gdbserver-xen in dom0, and ran my kernel modules in both dom0 and a domU. The kernel modules are essentially a frontend (in domU) and a backend (in dom0) driver. 2. I then debugged the frontend in dom0 3. My code runs normally (at least, I didn''t see anything wrong). After I debugged the code, I did ctrl+c to terminate gdbserver-xen, dom0 immediatelly reboot, which is not expected. Any solution to this problem? Another question: is there any way to debug the kernel module running in dom0? gdbserver-xen seems to only debug domU. Again, thanks a lot for your help! -l On 3/7/07, Markus Armbruster <armbru@redhat.com> wrote:> > "Lily Huang" <ushuanglily@gmail.com> writes: > > > Hi, > > > > I followed the instructions in tools/debugger/gdb/README to enable the > xen > > debugging feature. But after that my system (a kernel module) works 10 > times > > slower. Maybe the debugger slows down the running. > > > > What''s the right way to reverse and disable the debugger? I tried to > disable > > the "Kernel hacking -> Compile the kernel with debug info [*]" option. > But it > > does not help. Any ideas? > > Just terminate gdbserver-xen. > > If that doesn''t do it: What are your exact steps from `runs normally'' > to `runs slowly''? >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
"Lily Huang" <ushuanglily@gmail.com> writes:> Thanks a lot for your help! I already found the problem. My system is slowed > down because of misconfiguration, nothing to do with the debugger. > > But another funny thing for me is that once I used ctrl+c to terminate > gdbserver-xen, the dom0 will immediately reboot. My setting is as follows: > 1. I ran gdbserver-xen in dom0, and ran my kernel modules in both dom0 and a > domU. The kernel modules are essentially a frontend (in domU) and a backend (in > dom0) driver. > 2. I then debugged the frontend in dom0 > 3. My code runs normally (at least, I didn''t see anything wrong). > > After I debugged the code, I did ctrl+c to terminate gdbserver-xen, dom0 > immediatelly reboot, which is not expected. Any solution to this problem?That''s not supposed to happen. Anything in the logs or on the console? Serial console helps with capturing stuff.> Another question: is there any way to debug the kernel module running in dom0? > gdbserver-xen seems to only debug domU.I haven''t tried that.> Again, thanks a lot for your help!You''re welcome :) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel