public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/10350] thread-safety problem in std::string.
       [not found] <bug-10350-4@http.gcc.gnu.org/bugzilla/>
@ 2014-02-16 13:17 ` jackie.rosen at hushmail dot com
  2014-02-16 13:39 ` owner at bugs dot debian.org
  2014-02-17 18:18 ` owner at bugs dot debian.org
  2 siblings, 0 replies; 10+ messages in thread
From: jackie.rosen at hushmail dot com @ 2014-02-16 13:17 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10350

Jackie Rosen <jackie.rosen at hushmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jackie.rosen at hushmail dot com

--- Comment #10 from Jackie Rosen <jackie.rosen at hushmail dot com> ---
*** Bug 260998 has been marked as a duplicate of this bug. ***
Seen from the domain http://volichat.com
Page where seen: http://volichat.com/adult-chat-rooms
Marked for reference. Resolved as fixed @bugzilla.


^ permalink raw reply	[flat|nested] 10+ messages in thread

* [Bug libstdc++/10350] thread-safety problem in std::string.
       [not found] <bug-10350-4@http.gcc.gnu.org/bugzilla/>
  2014-02-16 13:17 ` [Bug libstdc++/10350] thread-safety problem in std::string jackie.rosen at hushmail dot com
@ 2014-02-16 13:39 ` owner at bugs dot debian.org
  2014-02-17 18:18 ` owner at bugs dot debian.org
  2 siblings, 0 replies; 10+ messages in thread
From: owner at bugs dot debian.org @ 2014-02-16 13:39 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10350

--- Comment #11 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Debian GCC Maintainers <debian-gcc@lists.debian.org>

If you wish to submit further information on this problem, please
send it to 140201@bugs.debian.org.

Please do not send mail to owner@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.


^ permalink raw reply	[flat|nested] 10+ messages in thread

* [Bug libstdc++/10350] thread-safety problem in std::string.
       [not found] <bug-10350-4@http.gcc.gnu.org/bugzilla/>
  2014-02-16 13:17 ` [Bug libstdc++/10350] thread-safety problem in std::string jackie.rosen at hushmail dot com
  2014-02-16 13:39 ` owner at bugs dot debian.org
@ 2014-02-17 18:18 ` owner at bugs dot debian.org
  2 siblings, 0 replies; 10+ messages in thread
From: owner at bugs dot debian.org @ 2014-02-17 18:18 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10350

--- Comment #12 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Debian GCC Maintainers <debian-gcc@lists.debian.org>

If you wish to submit further information on this problem, please
send it to 140201@bugs.debian.org.

Please do not send mail to owner@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.


^ permalink raw reply	[flat|nested] 10+ messages in thread

* [Bug libstdc++/10350] thread-safety problem in std::string.
       [not found] <20030408161601.10350.jkanze@caicheuvreuse.com>
                   ` (5 preceding siblings ...)
  2003-08-10  3:23 ` pinskia at gcc dot gnu dot org
@ 2005-05-02 13:32 ` pcarlini at suse dot de
  6 siblings, 0 replies; 10+ messages in thread
From: pcarlini at suse dot de @ 2005-05-02 13:32 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From pcarlini at suse dot de  2005-05-02 13:32 -------


*** This bug has been marked as a duplicate of 21334 ***

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |DUPLICATE


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10350


^ permalink raw reply	[flat|nested] 10+ messages in thread

* [Bug libstdc++/10350] thread-safety problem in std::string.
       [not found] <20030408161601.10350.jkanze@caicheuvreuse.com>
                   ` (4 preceding siblings ...)
  2003-08-10  3:22 ` pinskia at gcc dot gnu dot org
@ 2003-08-10  3:23 ` pinskia at gcc dot gnu dot org
  2005-05-02 13:32 ` pcarlini at suse dot de
  6 siblings, 0 replies; 10+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2003-08-10  3:23 UTC (permalink / raw)
  To: gcc-bugs

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10350


pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement


^ permalink raw reply	[flat|nested] 10+ messages in thread

* [Bug libstdc++/10350] thread-safety problem in std::string.
       [not found] <20030408161601.10350.jkanze@caicheuvreuse.com>
                   ` (3 preceding siblings ...)
  2003-06-28 19:15 ` pinskia at physics dot uc dot edu
@ 2003-08-10  3:22 ` pinskia at gcc dot gnu dot org
  2003-08-10  3:23 ` pinskia at gcc dot gnu dot org
  2005-05-02 13:32 ` pcarlini at suse dot de
  6 siblings, 0 replies; 10+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2003-08-10  3:22 UTC (permalink / raw)
  To: gcc-bugs

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10350


pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |140201 at bugs dot debian
                   |                            |dot org


------- Additional Comments From pinskia at gcc dot gnu dot org  2003-08-10 03:22 -------
*** Bug 9069 has been marked as a duplicate of this bug. ***


^ permalink raw reply	[flat|nested] 10+ messages in thread

* [Bug libstdc++/10350] thread-safety problem in std::string.
       [not found] <20030408161601.10350.jkanze@caicheuvreuse.com>
                   ` (2 preceding siblings ...)
  2003-06-11 15:43 ` dhazeghi@yahoo.com
@ 2003-06-28 19:15 ` pinskia at physics dot uc dot edu
  2003-08-10  3:22 ` pinskia at gcc dot gnu dot org
                   ` (2 subsequent siblings)
  6 siblings, 0 replies; 10+ messages in thread
From: pinskia at physics dot uc dot edu @ 2003-06-28 19:15 UTC (permalink / raw)
  To: gcc-bugs

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10350


pinskia at physics dot uc dot edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
     Ever Confirmed|                            |1
   Last reconfirmed|0000-00-00 00:00:00         |2003-06-28 19:15:53
               date|                            |


------- Additional Comments From pinskia at physics dot uc dot edu  2003-06-28 19:15 -------
Should not be in waiting.


^ permalink raw reply	[flat|nested] 10+ messages in thread

* [Bug libstdc++/10350] thread-safety problem in std::string.
       [not found] <20030408161601.10350.jkanze@caicheuvreuse.com>
  2003-06-08  8:27 ` dhazeghi@yahoo.com
  2003-06-09 16:29 ` bkoz@redhat.com
@ 2003-06-11 15:43 ` dhazeghi@yahoo.com
  2003-06-28 19:15 ` pinskia at physics dot uc dot edu
                   ` (3 subsequent siblings)
  6 siblings, 0 replies; 10+ messages in thread
From: dhazeghi@yahoo.com @ 2003-06-11 15:43 UTC (permalink / raw)
  To: gcc-bugs

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10350


dhazeghi@yahoo.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pcarlini@unitus.it


------- Additional Comments From dhazeghi@yahoo.com  2003-06-11 15:43 -------
Paolo,

Ben suggested that I contact you about this bug report. Is this in fact a defect of libstdc++, or is 
this behavior intended? Thanks,

Dara


^ permalink raw reply	[flat|nested] 10+ messages in thread

* [Bug libstdc++/10350] thread-safety problem in std::string.
       [not found] <20030408161601.10350.jkanze@caicheuvreuse.com>
  2003-06-08  8:27 ` dhazeghi@yahoo.com
@ 2003-06-09 16:29 ` bkoz@redhat.com
  2003-06-11 15:43 ` dhazeghi@yahoo.com
                   ` (4 subsequent siblings)
  6 siblings, 0 replies; 10+ messages in thread
From: bkoz@redhat.com @ 2003-06-09 16:29 UTC (permalink / raw)
  To: gcc-bugs

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10350



------- Additional Comments From bkoz@redhat.com  2003-06-09 16:29 -------
Subject: Re:  thread-safety problem in std::string.


>would you mind commenting on this? I gathered from recent list postings
>that thread safety is not necessarily a requirement for libstdc++...
>Thanks,

Paolo is the string maintainer, ask him.

-benjamin


^ permalink raw reply	[flat|nested] 10+ messages in thread

* [Bug libstdc++/10350] thread-safety problem in std::string.
       [not found] <20030408161601.10350.jkanze@caicheuvreuse.com>
@ 2003-06-08  8:27 ` dhazeghi@yahoo.com
  2003-06-09 16:29 ` bkoz@redhat.com
                   ` (5 subsequent siblings)
  6 siblings, 0 replies; 10+ messages in thread
From: dhazeghi@yahoo.com @ 2003-06-08  8:27 UTC (permalink / raw)
  To: gcc-bugs

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10350


dhazeghi@yahoo.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bkoz@gcc.gnu.org
             Status|UNCONFIRMED                 |WAITING
  GCC build triplet|                            |i686-pc-linux-gnu
   GCC host triplet|                            |i686-pc-linux-gnu
 GCC target triplet|                            |i686-pc-linux-gnu


------- Additional Comments From dhazeghi@yahoo.com  2003-06-08 08:20 -------
Ben,

would you mind commenting on this? I gathered from recent list postings that thread safety is not 
necessarily a requirement for libstdc++... Thanks,

Dara


^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2014-02-17 18:18 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-10350-4@http.gcc.gnu.org/bugzilla/>
2014-02-16 13:17 ` [Bug libstdc++/10350] thread-safety problem in std::string jackie.rosen at hushmail dot com
2014-02-16 13:39 ` owner at bugs dot debian.org
2014-02-17 18:18 ` owner at bugs dot debian.org
     [not found] <20030408161601.10350.jkanze@caicheuvreuse.com>
2003-06-08  8:27 ` dhazeghi@yahoo.com
2003-06-09 16:29 ` bkoz@redhat.com
2003-06-11 15:43 ` dhazeghi@yahoo.com
2003-06-28 19:15 ` pinskia at physics dot uc dot edu
2003-08-10  3:22 ` pinskia at gcc dot gnu dot org
2003-08-10  3:23 ` pinskia at gcc dot gnu dot org
2005-05-02 13:32 ` pcarlini at suse dot de

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).