Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: gdb debugging SIGEV_THREAD threads?
Date: Tue, 02 Aug 2005 22:44:55 +0800	[thread overview]
Message-ID: <42EF86E7.40506@tausq.org> (raw)
In-Reply-To: <20050802134128.GC9703@systemhalted.org>

> Might you have a clue as to why gdb can't debug a SIGEV_THREAD?
> This test fails with a SIGSEGV in NPTL. The thread is in
> __deallocate_stack (DSO address check from fault) 

Not a clue, but I can look into it.

randolph
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2005-08-02 14:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-02 13:41 [parisc-linux] gdb debugging SIGEV_THREAD threads? Carlos O'Donell
2005-08-02 14:44 ` Randolph Chung [this message]
2005-08-02 15:25   ` [parisc-linux] " Carlos O'Donell

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=42EF86E7.40506@tausq.org \
    --to=randolph@tausq.org \
    --cc=carlos@systemhalted.org \
    --cc=parisc-linux@lists.parisc-linux.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