public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: jlquinn@optonline.net To: jlquinn@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/9828: Regression: Segmentation fault in num_put::put Date: Tue, 25 Mar 2003 13:46:00 -0000 [thread overview] Message-ID: <20030325134600.18378.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/9828; it has been noted by GNATS. From: jlquinn@optonline.net To: Paolo Carlini <pcarlini@unitus.it> Cc: gcc-gnats@gcc.gnu.org, peturr02@ru.is, gcc-bugs@gcc.gnu.org, jlquinn@gcc.gnu.org Subject: Re: libstdc++/9828: Regression: Segmentation fault in num_put::put Date: Tue, 25 Mar 2003 08:34:28 -0500 Paolo Carlini writes: > Hi Jerry, > > on i686-pc-linux-gnu it's very easy to reproduce here, no special options, both > 3.3 and 3.4. The seg fault happens when _M_group_int tries to use __grouping, > in particular __grouping.size(). In _M_convert_int, __lc._M_use_grouping is equal > to 4 (true), but __lc._M_grouping is not a valid string: > > (gdb) print __lc._M_grouping.data() > $3 = 0x0 > > Paolo. Huh. WHat I had done was check out 3.3 on i686-pc-linux-gnu, and configure --with-system-zlib --enable-threads --with-cpu=athlon --program-suffix=3.3. I can rebootstrap with no options and see what happens. > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9828 >
next reply other threads:[~2003-03-25 13:46 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-25 13:46 jlquinn [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-03 16:36 Benjamin Kosnik 2003-04-03 16:26 Benjamin Kosnik 2003-04-03 16:16 Benjamin Kosnik 2003-04-03 15:46 Pétur Runólfsson 2003-04-03 14:46 Jerry Quinn 2003-03-25 13:15 Paolo Carlini 2003-03-25 13:06 Paolo Carlini 2003-03-25 6:46 Jerry Quinn 2003-03-24 13:41 paolo 2003-02-24 9:26 peturr02
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=20030325134600.18378.qmail@sources.redhat.com \ --to=jlquinn@optonline.net \ --cc=gcc-prs@gcc.gnu.org \ --cc=jlquinn@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: linkBe 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).