linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Achim Machura" <achim.machura@berghof.com>
To: "'Mark Chambers'" <markc@mail.com>
Cc: "Linuxppc-Embedded \(E-Mail\)" <linuxppc-embedded@ozlabs.org>
Subject: AW: pthread debugging problem
Date: Mon, 25 Apr 2005 08:51:20 +0200	[thread overview]
Message-ID: <000501c54963$306766c0$34f1ff0a@beint.local> (raw)
In-Reply-To: <002101c54774$83c85590$0301a8c0@chuck2>

Hello Mark,

-----Ursprüngliche Nachricht-----
Von: linuxppc-embedded-bounces@ozlabs.org
[mailto:linuxppc-embedded-bounces@ozlabs.org]Im Auftrag von Mark Chambers
Gesendet: Freitag, 22. April 2005 21:50
An: linuxppc-embedded@ozlabs.org
Betreff: pthread debugging problem


<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.

Sometimes we have the same problems.
We have solved it by telling gdb the path of the libs using,
set SOLIB_ABSOLUTE_PREFIX.
Also there is a problem if you use different versions of dynamic libraries
for the progamm and the gdb.

achim

      reply	other threads:[~2005-04-25  7:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-22 19:50 pthread debugging problem Mark Chambers
2005-04-25  6:51 ` Achim Machura [this message]

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='000501c54963$306766c0$34f1ff0a@beint.local' \
    --to=achim.machura@berghof.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=markc@mail.com \
    /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).