From: Sam Ravnborg <sam@ravnborg.org>
To: linux-embedded@vger.kernel.org
Subject: debugging multi threaded applicatiosn on arm - status?
Date: Fri, 17 Jun 2011 11:39:27 +0200 [thread overview]
Message-ID: <20110617093927.GA28305@merkur.ravnborg.org> (raw)
Is it possible to bebug multi-threaded applications using gdb on ARM these days?
We have had trobules getting this to work - but I do not have the details at hand atm.
I am just curious if this is supposed to work or not.
We have an arm target running: 2.6.32.8 #1 PREEMPT
CPU: ARM926EJ-S rev 5 (v5l) (Atmel AT91SAM9263)
The kernel is only lightly modifed - mostly with a few
propriatary drivers and a few driver hacks (not suitable for mainline).
It is a long story why we use such an old version.
Our applications uses threads and we use glibc 2.10.1 with NPTL enabled.
So far we have survived using the powerfull printf debugging :-)
Sam
next reply other threads:[~2011-06-17 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 9:39 Sam Ravnborg [this message]
2011-06-17 12:46 ` debugging multi threaded applicatiosn on arm - status? Chris Simmonds
2011-06-17 15:39 ` Sam Ravnborg
2011-10-09 9:55 ` Peter Waechtler
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=20110617093927.GA28305@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-embedded@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).