public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pcarlini at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/29179] bugs in mt_allocator
Date: Fri, 22 Sep 2006 14:48:00 -0000 [thread overview]
Message-ID: <20060922144825.14234.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29179-13287@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from pcarlini at suse dot de 2006-09-22 14:48 -------
(In reply to comment #4)
> ok, perhaps this is not really a bug, however segfault is not very user
> friendly. could ASSERT solve it?
No, we don't have asserts anywhere, for various reasons. Really, the
documentation must be asjusted and then the user *must* carefully follow it.
This piece of code is only for espert usage, not for novices, this should be
clear.
> about the first one, I take it you agree that it is a real bug?
Yes, the documentation must be slightly adjusted to 32767.
--
pcarlini at suse dot de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2006-09-22 14:48:24
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29179
next prev parent reply other threads:[~2006-09-22 14:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 10:31 [Bug c++/29179] New: " random at adriver dot ru
2006-09-22 11:19 ` [Bug libstdc++/29179] " pcarlini at suse dot de
2006-09-22 13:32 ` random at adriver dot ru
2006-09-22 13:42 ` pcarlini at suse dot de
2006-09-22 14:40 ` random at adriver dot ru
2006-09-22 14:48 ` pcarlini at suse dot de [this message]
2006-09-22 16:04 ` pinskia at gcc dot gnu dot org
2006-09-25 10:05 ` paolo at gcc dot gnu dot org
2006-09-25 10:06 ` paolo at gcc dot gnu dot org
2006-09-25 10:07 ` pcarlini at suse dot de
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=20060922144825.14234.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).