From: Andrew Cagney <ac131313@cygnus.com>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: [PATCH RFA] process/thread/lwp identifier mega-patch
Date: Fri, 16 Feb 2001 06:29:00 -0000 [thread overview]
Message-ID: <3A8D3823.8CA8D470@cygnus.com> (raw)
In-Reply-To: <1001204163129.ZM1315@ocotillo.lan>
Kevin Buettner wrote:
> [...]
Kevin,
One thought on this (prompted by a side conversation). From memory you
had concerns with your memory [groan] (i.e. memory leaks).
Have you considered ignoring the problem? Well actually just
accumulating a list of all the created threads and then, when GDB
re-starts a target, deleting the lot? Yes, this will clearly not scale
well in an application that creates then deletes millions of threads.
Hopefully though, the benefits (such as improved performance) of having
per thread objects will far out way this.
I suspect that the way GDB currently tries to delete threads is
technically flawed - it only worked because there was really only one
thread. A better more robust model needs to be developed but I don't
think solving that problem should be part of this patch. The person
with the million threads can solve that one :-)
Andrew
next parent reply other threads:[~2001-02-16 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1001003083922.ZM18831@ocotillo.lan>
[not found] ` <3A196C0E.B28DA29@cygnus.com>
[not found] ` <1001120185800.ZM17272@ocotillo.lan>
[not found] ` <3A1E4BE8.866BCBED@cygnus.com>
[not found] ` <3A2748DF.206B4418@eazel.com>
[not found] ` <1001204163129.ZM1315@ocotillo.lan>
2001-02-16 6:29 ` Andrew Cagney [this message]
2001-02-16 11:07 ` Kevin Buettner
2001-02-16 14:19 ` Andrew Cagney
2001-02-16 15:03 ` Kevin Buettner
2001-02-17 10:51 ` Andrew Cagney
2001-02-17 11:31 Michael Elizabeth Chastain
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=3A8D3823.8CA8D470@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=kevinb@cygnus.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