public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: lprimak@hope.nyc.ny.us
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/7168: C++ Exceptions in Multithreaded Applications Crash (cygwin)
Date: Sat, 29 Jun 2002 15:46:00 -0000	[thread overview]
Message-ID: <20020629213927.3900.qmail@sources.redhat.com> (raw)


>Number:         7168
>Category:       libstdc++
>Synopsis:       C++ Exceptions in Multithreaded Applications Crash (cygwin)
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jun 29 14:46:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Lenny Primak
>Release:        2.95.3-5 (cygwin special)
>Organization:
>Environment:
Cygwin stock cygwin.com 1.3 install, MS Windows  (any)
>Description:
Superceeds gnats/7167,
using the C++ exception system from multiple threads corrupts the gcc's internal exception stack, due to not including the thread-specific exception context in the compile.
>How-To-Repeat:
The attached program will determine whether the exception context is thread-specific or not
>Fix:
Looking for one
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="gcc_exception.C"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="gcc_exception.C"

I2luY2x1ZGUgPHN0ZGlvLmg+CiNpbmNsdWRlIDxwdGhyZWFkLmg+CiNpbmNsdWRlIDxzeXMvcG9s
bC5oPgoKCmV4dGVybiAiQyIgdm9pZCAqCl9fZ2V0X2VoX2NvbnRleHQgKCk7CgoKc3RhdGljIHZv
aWQqIHNhdmVkX2VoX2NvbnRleHQgPSAwOwoKc3RhdGljIHZvaWQqIGZ1bmModm9pZCopIHRocm93
KGNoYXIqKQp7Cgl2b2lkKiBlaF9jbnR4dCA9IF9fZ2V0X2VoX2NvbnRleHQoKTsKCXByaW50Zigi
ZnVuYygpIC0gZWhfY29udGV4dCA9ICVYXG4iLCBlaF9jbnR4dCk7CglpZihzYXZlZF9laF9jb250
ZXh0ID09IDApCgl7CgkJc2F2ZWRfZWhfY29udGV4dCA9IGVoX2NudHh0OwoJfQoJZWxzZQoJewoJ
CWlmKGVoX2NudHh0ID09IHNhdmVkX2VoX2NvbnRleHQpCgkJewoJCQlwcmludGYoIkZBVEFMOiBJ
ZGVudGljYWwgRXhjZXB0aW9uIFN0YWNrcyFcbiIpOwoJCX0KCQllbHNlCgkJewoJCQlwcmludGYo
IkdyZWF0ISBFeGNlcHRpb24gU3RhY2tzIERpZmZlci5cbiIpOwoJCX0KCX0KCWludCBzdmFyID0g
NTsKCXRyeSB7CgkJdGhyb3cgMTsKCX0KCWNhdGNoKGNoYXIqKQoJewoJCXByaW50ZigiY2F1Z2h0
IHN0cmluZ1xuIik7Cgl9CgljYXRjaChpbnQpCgl7CgkJLy8gbm90aGluZwoJfQoKCXBvbGwoMCwg
MCwgNTAwMCk7CglyZXR1cm4gMDsKfQoKaW50IG1haW4oKQp7CglwdGhyZWFkX3QgdGhyLCB0aHIy
OwoJcHRocmVhZF9jcmVhdGUoJnRociwgMCwgJmZ1bmMsIDApOwoJcG9sbCgwLCAwLCAxMDAwKTsK
CXB0aHJlYWRfY3JlYXRlKCZ0aHIyLCAwLCAmZnVuYywgMCk7CglwdGhyZWFkX2pvaW4odGhyLCAw
KTsKCXB0aHJlYWRfam9pbih0aHIyLCAwKTsKCXJldHVybiAwOwp9Cg==


             reply	other threads:[~2002-06-29 21:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-29 15:46 lprimak [this message]
2002-07-01 15:46 Phil Edwards
2002-07-01 21:16 Lenny Primak
2002-07-03  9:38 bkoz
2002-07-03 10:26 Lenny Primak
2002-07-03 10:56 Lenny Primak
2002-07-03 10:56 Benjamin Kosnik
2002-07-10 19:26 Lenny Primak
2002-07-25 13:15 bkoz

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=20020629213927.3900.qmail@sources.redhat.com \
    --to=lprimak@hope.nyc.ny.us \
    --cc=gcc-gnats@gcc.gnu.org \
    /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).