From: Jan Kiszka <jan.kiszka@domain.hid>
To: Stephen Davies <steve_davies61@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Debugger Support
Date: Thu, 15 Jan 2009 12:48:17 +0100 [thread overview]
Message-ID: <496F2281.2000102@domain.hid> (raw)
In-Reply-To: <BAY101-W2825402A319CC124388542EAD70@domain.hid>
Stephen Davies wrote:
> Hi All,
>
> I currently have an application that runs under RTAI however I am now
> having problems that I wish to debug. Debugger support for RTAI is
> limited at best (currently the only option we have is to use
> rt_printk() or printf() to the console). I've been looking back at
> Xenomai and I see a lot of references to LTTng support which would be
> ideal and would mean I would port my RTAI app to Xenomai. However
> these references seem to all die out around 2007. Is there still
> support for a "proper" debugger (stepping through code, variable
> values etc...) in the current release of Xenomai?
LTTng is actively supported over Xenomai, we just still need additional
fiddling with the patch series as LTTng is not yet mainline. We are
using it here over 2.6.26 ATM, I think I just missed to post the (rather
simple) update from the published 2.6.24 version. And I'm about to port
them to the next kernel base (either 2.6.27 or .28).
Beside the LTTng tracer there is also source-level debugging, of course.
gdb for the apps, kgdb for the kernel (x86) - or via KVM, ie. kernel
source-level debugging inside a virtual x86 machine. kgdb just needs
some extra patches which I didn't update to 2.6.27 yet because I'm using
KVM now.
Jan
--
Siemens AG, Corporate Technology, CT SE 26
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-01-15 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 10:56 [Xenomai-help] Debugger Support Stephen Davies
2009-01-15 11:48 ` Jan Kiszka [this message]
2009-01-15 12:38 ` Stephen Davies
2009-01-15 13:29 ` Jan Kiszka
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=496F2281.2000102@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=steve_davies61@domain.hid \
--cc=xenomai@xenomai.org \
/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.