From: "Mark Chambers" <markc@mail.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: pthread debugging problem
Date: Fri, 22 Apr 2005 15:50:18 -0400 [thread overview]
Message-ID: <002101c54774$83c85590$0301a8c0@chuck2> (raw)
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
I am debugging a simple program with several threads, using pthreads.
printf's tell me that the threading is working, but I am unable to debug
the program with gdb (gdbserver on the target). I get spurious
'Program received signal SIG32, Real-time even 32' messages.
I'm using a stock ELDK tree via NFS boot. I couldn't tell you the ELDK
version but I've listed some of the components below.
I've found postings in the general linux community, but they don't seem
to apply in this case. I've compiled a late gdb (6.2), tried later versions
of all the libraries that seem relevant, to no avail. Any ideas? Or,
equally valuable, is anybody debugging pthreads successfully on ppc,
what is your setup?
Thanks,
Mark Chambers
versions:
libc-2.2.1
libpthread-0.9.so
kernel - 2.4.19
[-- Attachment #2: Type: text/html, Size: 1986 bytes --]
next reply other threads:[~2005-04-22 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 19:50 Mark Chambers [this message]
2005-04-25 6:51 ` AW: pthread debugging problem Achim Machura
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='002101c54774$83c85590$0301a8c0@chuck2' \
--to=markc@mail.com \
--cc=linuxppc-embedded@ozlabs.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 NNTP newsgroup(s).