public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Bruce Korb <bkorb@pacbell.net>
Cc: insight@sources.redhat.com
Subject: Re: multi-threaded debugging using Insight
Date: Thu, 03 Oct 2002 10:35:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0210031035140.1509-100000@valrhona.uglyboxes.com> (raw)
In-Reply-To: <3D9C7E35.FB1AC2A6@pacbell.net>

On Thu, 3 Oct 2002, Bruce Korb wrote:

> > This is version 5.2.1:
> > 
> > (gdb) set args man2html.cat1
> > (gdb) r
> > Starting program: /home/bkorb/tools/man2html/man2html man2html.cat1
> > [New Thread 1024 (LWP 1930)]
> > [New 
> > Error: Cannot find thread 2049: invalid thread handle
> > 
> > (gdb)

> 
> See:
> http://sources.redhat.com/ml/insight/2002-q3/msg00185.html
> 
> That message was copied to gdb@sources.redhat.com, but there
> were no replies from anyone.  After this point in the debugging,
> I cannot do anything at all.  If I avoid the popen call, then
> I don't see this problem.  Pretty sure there must be a connection  :-)
> The platform is Linux 2.4.18 on i686 using whatever GCC SuSE shipped
> with 8.0.

Ah, yes, I remember this now. You're going to have to keep pinging the GDB 
folks at gdb@sources.redhat.com. There are far more people there that can 
help you with this than there are here. (In case there's any doubt, this 
mailing list is essentially just me, with a tiny smattering of input 
from others.) The GDB list has dozens of active contributors/developers.

Have you tried 5.3 or CVS head?

Keith


      reply	other threads:[~2002-10-03 17:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-02 22:22 Remote debug " Masahide Tomita
2002-10-03  8:40 ` Keith Seitz
2002-10-03  8:54   ` multi-threaded debugging " Bruce Korb
2002-10-03  9:01     ` Keith Seitz
2002-10-03 10:28       ` Bruce Korb
2002-10-03 10:35         ` Keith Seitz [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=Pine.LNX.4.44.0210031035140.1509-100000@valrhona.uglyboxes.com \
    --to=keiths@redhat.com \
    --cc=bkorb@pacbell.net \
    --cc=insight@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).