public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: GDB, pthreads, and kernel threads
Date: Wed, 18 May 2005 18:14:14 -0600	[thread overview]
Message-ID: <428BDA56.5030502@shaw.ca> (raw)
In-Reply-To: <45zKO-3RV-45@gated-at.bofh.it>

John Clark wrote:
> I built the latest GDB-6.3, as well as rebuilt glibc-2.3.5, and now when 
> I step through the
> main code line, which creates the tasks (I'm using the pthreads.c from 
> the GDB testsuite), I do
> not getany output from:
> 
> info threads
> 
> When I set a break point on the entry point of one of the 
> soon-to-be-created threads,
> I get a diagnostic message:
> 
> Program terminated with signal SIGTRAP, Trace/Breakpoint trap.
> The program no longer exists.

Are you sure your glibc and gdb were both configured to support threads 
when they were compiled?

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2005-05-19  0:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <45k9a-7DD-11@gated-at.bofh.it>
     [not found] ` <45xIX-2bR-31@gated-at.bofh.it>
     [not found]   ` <45zKO-3RV-45@gated-at.bofh.it>
2005-05-19  0:14     ` Robert Hancock [this message]
2005-05-19  0:36       ` GDB, pthreads, and kernel threads Ajay Patel
2005-05-19 16:22       ` John Clark
2005-05-19 16:52         ` Douglas McNaught
2005-05-19 17:27           ` John Clark
2005-05-19 17:02         ` Ajay Patel
2005-05-17 23:37 John Clark
2005-05-18 14:01 ` Nix
2005-05-18 15:53   ` John Clark

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=428BDA56.5030502@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=linux-kernel@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