From: Bruce Korb <bkorb@pacbell.net>
To: Keith Seitz <keiths@redhat.com>, gdb@sources.redhat.com
Cc: insight@sources.redhat.com, bkorb@pacbell.net
Subject: Re: Error: Cannot find thread 2049: invalid thread handle
Date: Tue, 24 Sep 2002 09:40:00 -0000 [thread overview]
Message-ID: <3D90967B.A0B56595@pacbell.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0209240915020.1493-100000@lindt.uglyboxes.com>
Keith Seitz wrote:
>
> > (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
>
> If you've done this while running the command line (gdb -nw), then you
> should ask on gdb@sources.redhat.com, since this is a backend problem
> wothj gdb.
That is from the console window from Insight.
I have no particular clue about whether it is an
Insight problem or a GDB problem. I am certain that
the problem stems from using ``popen( "...", "r" );''
prev parent reply other threads:[~2002-09-24 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 18:17 Bruce Korb
2002-09-24 9:04 ` Keith Seitz
2002-09-24 9:40 ` Bruce Korb [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=3D90967B.A0B56595@pacbell.net \
--to=bkorb@pacbell.net \
--cc=gdb@sources.redhat.com \
--cc=insight@sources.redhat.com \
--cc=keiths@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).