public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Paolo Carlini <pcarlini@unitus.it>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/8840: 3.2.1: sort (v.begin (), v.end (), loc) dumps core
Date: Fri, 06 Dec 2002 06:06:00 -0000	[thread overview]
Message-ID: <20021206140609.21999.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/8840; it has been noted by GNATS.

From: Paolo Carlini <pcarlini@unitus.it>
To: Franz Gans <franz.gans.entenhausen@t-online.de>
Cc: paolo@gcc.gnu.org,  gcc-bugs@gcc.gnu.org,  gcc-prs@gcc.gnu.org, 
 nobody@gcc.gnu.org,  gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/8840: 3.2.1: sort (v.begin (), v.end (), loc) dumps
 core
Date: Fri, 06 Dec 2002 15:04:51 +0100

 Franz Gans wrote:
 
 > Do I have to upgrade to 2.2.5?
 
 Well, right now now I cannot tell for sure if the problem is due to a 
 bug in glibc2.2.4, fixed in 2.2.5.
 
 However, from my own experience, upgrading from 2.2.4 to 2.2.5 is safe 
 and worthy, in general.
 
 Also, it would be nice if you could test your code on a glibc2.3.x 
 system like mine.
 
 Ciao,
 Paolo.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8840
 
 
 
 
 
 


             reply	other threads:[~2002-12-06 14:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06  6:06 Paolo Carlini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-06 20:43 bkoz
2002-12-11  9:04 bkoz
2002-12-06  9:16 Paolo Carlini
2002-12-06  6:06 Franz Gans
2002-12-06  6:05 paolo
2002-12-06  4:14 paolo
2002-12-06  3:16 franz.gans.entenhausen

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=20021206140609.21999.qmail@sources.redhat.com \
    --to=pcarlini@unitus.it \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).