public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Andrey Slepuhin <pooh@msu.ru>
To: (H.J. Lu) <hjl@lucon.org>
Cc: egcs-bugs@egcs.cygnus.com, (GNU C Library) <libc-hacker@cygnus.com>
Subject: RE: A patch for linuxthreads
Date: Wed, 17 Mar 1999 04:52:00 -0000	[thread overview]
Message-ID: <XFMail.990317155239.pooh@msu.ru> (raw)
In-Reply-To: <m10N7wN-000ErMC@ocean.lucon.org>

On 17-Mar-99 H.J. Lu wrote:
> Hi,
> 
> This Linuxthreads patch should fix
> 
> http://egcs.cygnus.com/ml/egcs-bugs/1999-03/msg00316.html
> 
> The problem is we should not access those key data stuctures after
> a thread is terminared since they have been freed.

Does this mean that your previous message
( http://egcs.cygnus.com/ml/egcs-bugs/1999-03/msg00461.html )
was wrong or egcs still has a separate bug in thread-safe EH?
If so, do you have a testcase?

Regards,
Andrey.

  parent reply	other threads:[~1999-03-17  4:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-16 20:28 H.J. Lu
1999-03-17  2:20 ` Mark Kettenis
1999-03-17  7:21   ` H.J. Lu
1999-03-17  4:52 ` Andrey Slepuhin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-09-04 10:48 H . J . Lu
2000-09-04 19:54 ` Ulrich Drepper
1999-12-16 16:12 H . J . Lu
     [not found] ` <199912170033.QAA01416@localhost.cygnus.com>
1999-12-16 16:43   ` H . J . Lu
1999-04-14 22:31 H.J. Lu
1999-04-14 23:51 ` Ulrich Drepper
1999-03-17 13:44 Mike Stump
1999-03-18  7:44 ` H.J. Lu
1998-12-02 10:35 H.J. Lu
1998-12-02 11:44 ` Ulrich Drepper
1998-10-24 18:33 H.J. Lu
1998-10-25  0:59 ` Ulrich Drepper
1998-10-25  8:22   ` H.J. Lu
1998-10-25  8:22     ` Ulrich Drepper
1998-08-08 23:26 H.J. Lu
1998-08-09  8:59 ` Ulrich Drepper

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=XFMail.990317155239.pooh@msu.ru \
    --to=pooh@msu.ru \
    --cc=egcs-bugs@egcs.cygnus.com \
    --cc=hjl@lucon.org \
    --cc=libc-hacker@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).