From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4E30391C.2070007@domain.hid> Date: Wed, 27 Jul 2011 18:13:16 +0200 From: zenati MIME-Version: 1.0 References: <4E2EAB0F.6050109@domain.hid> <4E2FD923.2040003@domain.hid> <4E2FFE1B.5010900@domain.hid> <4E3000A6.7080001@domain.hid> In-Reply-To: <4E3000A6.7080001@domain.hid> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-core] Debugging Xenomai kernel List-Id: Xenomai life and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Xenomai core On 07/27/2011 02:12 PM, Jan Kiszka wrote: > On 2011-07-27 14:01, zenati wrote: >> On 07/27/2011 11:23 AM, Jan Kiszka wrote: >>> On 2011-07-26 13:54, zenati wrote: >>>> Dear, >>>> >>>> I'm trying to debug Xenomai kernel with GDB and Qemu. >>> QEMU in emulation or KVM mode? >>> >> I'm using Qemu in emulation mode. > What's your target arch? x84-64, x86-32, or some ARM or PPC etc. x86-32 >>>> So, I launch >>>> Xenomai in Qemu and make it waiting for GDB. Then I start GDB and >>>> connect them to Qemu, make breakpoint at the desired function to debug >>>> and start Xenomai. If the function belongs to the linux kernel, the >>>> execution stop at the breakpoint. But, if the function belongs to the >>>> Xenomai nucleus, GDB recognize the breakpoint at the execution but don't >>>> stop. >>> Is Xenomai built as module or part of the main kernel image? The latter >>> is simpler to handle as you don't have to deal with modules as symbol >>> sources, find out their addresses, and load them at the right location. >>> >> Xenomai is built as a part of the main kernel. > OK. Check during runtime of the guest if the disassembly at the desired > breakpoint address matches the compiled code. Maybe there is some > accidental discrepancy. The breakpoints match correctly the compiled code. Anyway, it must stop at the breakpoint. No? > Jan >