From: Mark Kettenis <kettenis@wins.uva.nl>
To: gdb@sourceware.cygnus.com, rok.papez@kiss.uni-lj.si,
blizzard@redhat.com, kevinb@cygnus.com, grg22@ai.mit.edu,
greg@mcgary.org, randy@dontknow.org, jgarza@metrowerks.com,
pnolan@dircon.co.uk, markusk@pvv.org, mikepery@fscked.org,
eric@atdesk.com, asheik4@cs.mcgill.ca
Subject: Linux threads support in GDB
Date: Sun, 03 Sep 2000 12:34:00 -0000 [thread overview]
Message-ID: <200009031934.e83JYDs02423@delius.kettenis.local> (raw)
To all who have reported problems with GDB's threads support on Linux,
Today, I've checked in a rewrite of GDB's threads support for Linux
into the GDB CVS tree. This should really make debugging
multi-threaded code more robust. However, to be sure that it really
is more robust, it needs to be tested. Multi-threaded code is
timing-critical and me not noticing any problems doesn't mean they are
not there. I welcome everybody to check out the new code and report
any problems. Please provide a (small) test program and enough
information to reproduce the problem if you do.
To avoid disappointments:
* You'll need glibc 2.1.3. Older versions are no longer supported.
* The new threads stuff is only enabled for Linux/x86.
* The "zombie problem" isn't fixed yet ...
* ... which doesn't really matter since the limit of ~30 threads
isn't fixed either.
* You'll see quite a bit of debugging output, that tells you (or me)
what's going on, but interferes with the program output.
See < http://sources.redhat.com/gdb > for information on how the check out
the code.
I'll be looking forward to your reports,
Mark
next reply other threads:[~2000-09-03 12:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-03 12:34 Mark Kettenis [this message]
[not found] <200009140024.e8E0OCK13917@mbox.wins.uva.nl>
2000-10-02 5:57 ` Mark Kettenis
2000-10-02 16:00 ` gdb
2000-10-02 16:15 ` gdb
2000-10-04 17:12 ` gdb
[not found] <200010022259.e92MxmK06653@mbox.wins.uva.nl>
2000-10-03 1:28 ` Mark Kettenis
[not found] <200010050012.CAA26158@mailhost.ri.silicomp.fr>
2000-10-04 22:50 ` Eric Paire
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=200009031934.e83JYDs02423@delius.kettenis.local \
--to=kettenis@wins.uva.nl \
--cc=asheik4@cs.mcgill.ca \
--cc=blizzard@redhat.com \
--cc=eric@atdesk.com \
--cc=gdb@sourceware.cygnus.com \
--cc=greg@mcgary.org \
--cc=grg22@ai.mit.edu \
--cc=jgarza@metrowerks.com \
--cc=kevinb@cygnus.com \
--cc=markusk@pvv.org \
--cc=mikepery@fscked.org \
--cc=pnolan@dircon.co.uk \
--cc=randy@dontknow.org \
--cc=rok.papez@kiss.uni-lj.si \
/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).