From: Frank McPherson <frank@mitre.org>
To: Claude Robitaille <crobitaille@videotron.ca>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Debugging with thread(s)
Date: Tue, 07 Dec 1999 08:14:29 -0500 [thread overview]
Message-ID: <384D0835.74F85CEC@mitre.org> (raw)
In-Reply-To: Pine.LNX.4.10.9912062143190.1956-100000@localhost.localdomain
Claude Robitaille wrote:
> anybody has tried to debug an application that uses thread
> using GUI frontend to gdb? ... I execute pthread_create I get an
> unknown signal and the breakpoints I set in the called
> (created) thread do not activate.
I get the same behavior when using gdb without any frontend. Pthreads
seems to use real-time signals (32 and higher), and though the
documentation for gdb indicates it should be able to handle them, I
haven't been able to get it to work. I posted a query about this
yesterday called "real-time signals, gdb".
It has been suggested to me by another list member that the signal
handling code in the Linux kernel may be seriously deficient, and
aggrevating if not outright causing this problem. I haven't had a
chance yet to look and see if that's the case.
Has anyone else had success debugging threads with gdb?
-Frank
--
Frank H. McPherson IV
W118 Embedded Solutions Team
The MITRE Corporation
703-883-5404
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-12-07 13:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-27 11:50 What's MMU context? Wang Yong
1999-10-27 15:55 ` Dan Malek
1999-12-07 2:58 ` Debugging with thread(s) Claude Robitaille
1999-12-07 13:14 ` Frank McPherson [this message]
1999-12-12 0:00 ` Thread and malloc Claude Robitaille
[not found] <0FMD0095OJDI5C@falla.videotron.net>
1999-12-08 0:59 ` Debugging with thread(s) Claude Robitaille
1999-12-08 8:38 ` Martin Costabel
[not found] ` <v04003a00b47368afb81b@[216.81.20.221]>
1999-12-08 13:14 ` Marcus Sundberg
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=384D0835.74F85CEC@mitre.org \
--to=frank@mitre.org \
--cc=crobitaille@videotron.ca \
--cc=linuxppc-dev@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 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).