All of lore.kernel.org
 help / color / mirror / Atom feed
From: zenati <omar.zenati@domain.hid>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: Xenomai core <Xenomai-core@domain.hid>
Subject: Re: [Xenomai-core] Debugging Xenomai kernel
Date: Wed, 27 Jul 2011 18:13:16 +0200	[thread overview]
Message-ID: <4E30391C.2070007@domain.hid> (raw)
In-Reply-To: <4E3000A6.7080001@domain.hid>

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
>



  reply	other threads:[~2011-07-27 16:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-26 11:54 [Xenomai-core] Debugging Xenomai kernel zenati
2011-07-27  9:23 ` Jan Kiszka
2011-07-27 12:01   ` zenati
2011-07-27 12:12     ` Jan Kiszka
2011-07-27 16:13       ` zenati [this message]
2011-07-27 16:16         ` Jan Kiszka
2011-07-27 16:53           ` zenati

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E30391C.2070007@domain.hid \
    --to=omar.zenati@domain.hid \
    --cc=Xenomai-core@domain.hid \
    --cc=jan.kiszka@domain.hid \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.