All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@lvl7.com>
To: Frank Haverkamp <f.haverkamp@web.de>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Debugging Multithreaded applications
Date: Wed, 20 Mar 2002 09:33:08 -0500	[thread overview]
Message-ID: <3C989DA4.E76C43A3@lvl7.com> (raw)
In-Reply-To: 200203201427.g2KERAv17415@mailgate5.cinetic.de


If your friends debug problems stem from the fact that when he does things like run his application in gdb, the breakpoints and backtraces don't seem to be correct, then I think his problem, is that he is running a pre v5.1 copy of gdb.  If I remember correctly, gdb 5.1 added features to better handle the debugging of multithreaded applications.  If the above behavior sounds familiar, I'd try getting the latest GDB.  Hope that helps!
Neil

Frank Haverkamp wrote:
>
> Hi,
>
> a friend of mine told me that he had problems debugging multithreaded
> applications on a powerpc Linux based platform. I think he is using
> glibc 2.1.3 and gcc-2.95.2 and libpthread-0.8.
>
> Does anybody has made experiences with that? Unfortunatly I have no
> more information about the system he is using. Are there any known
> problems with the gcc, glibc or libpthread concering debugging?
> Should he update? Which version should he than take?
>
> Which are the latest version of gcc, glibc and libpthread known to be
> working with powerpc Linux?
>
> Thanks,
>
> Frank
>
> --
> Frank Haverkamp
> f.haverkamp@web.de
> ________________________________________________________________
> Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr!
> Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13
>

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-03-20 14:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-20 14:27 Debugging Multithreaded applications Frank Haverkamp
2002-03-20 14:33 ` Neil Horman [this message]
2002-03-20 22:21 ` Rick Hunnicutt

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=3C989DA4.E76C43A3@lvl7.com \
    --to=nhorman@lvl7.com \
    --cc=f.haverkamp@web.de \
    --cc=linuxppc-embedded@lists.linuxppc.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.