public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/22139] [4.0/4.1 regression] Segfault Date: Tue, 21 Jun 2005 23:43:00 -0000 [thread overview] Message-ID: <20050621234337.16135.qmail@sourceware.org> (raw) In-Reply-To: <20050621175735.22139.bangerth@dealii.org> ------- Additional Comments From pinskia at gcc dot gnu dot org 2005-06-21 23:43 ------- This is the reason why ggc_free is considered a bad idea, because if this was really dead, it would have been GC'd already but it is not dead. And isn't the reason why we moved alway from what 2.95.3 did to the GC is so we don't have hard to debug problems like this? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22139
next prev parent reply other threads:[~2005-06-21 23:43 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-06-21 17:57 [Bug c++/22139] New: [4.1 " bangerth at dealii dot org 2005-06-21 17:57 ` [Bug c++/22139] " bangerth at dealii dot org 2005-06-21 17:58 ` bangerth at dealii dot org 2005-06-21 18:00 ` bangerth at dealii dot org 2005-06-21 18:03 ` bangerth at dealii dot org 2005-06-21 18:13 ` pinskia at gcc dot gnu dot org 2005-06-21 18:14 ` [Bug c++/22139] [4.0/4.1 " bangerth at dealii dot org 2005-06-21 18:36 ` pinskia at gcc dot gnu dot org 2005-06-21 18:41 ` pinskia at gcc dot gnu dot org 2005-06-21 18:43 ` pinskia at gcc dot gnu dot org 2005-06-21 18:48 ` bangerth at dealii dot org 2005-06-21 18:55 ` pinskia at gcc dot gnu dot org 2005-06-21 19:12 ` pinskia at gcc dot gnu dot org 2005-06-21 21:57 ` pinskia at gcc dot gnu dot org 2005-06-21 23:04 ` pinskia at gcc dot gnu dot org 2005-06-21 23:07 ` pinskia at gcc dot gnu dot org 2005-06-21 23:15 ` pinskia at gcc dot gnu dot org 2005-06-21 23:43 ` pinskia at gcc dot gnu dot org [this message] 2005-07-01 4:32 ` pinskia at gcc dot gnu dot org 2005-07-06 16:57 ` mmitchel at gcc dot gnu dot org 2005-07-06 17:04 ` mmitchel at gcc dot gnu dot org 2005-07-15 23:13 ` mmitchel at gcc dot gnu dot org 2005-07-15 23:27 ` pinskia at gcc dot gnu dot org 2005-07-16 3:11 ` pinskia at gcc dot gnu dot org 2005-07-16 4:02 ` reichelt at gcc dot gnu dot org 2005-07-16 8:32 ` pinskia at gcc dot gnu dot org 2005-07-17 20:56 ` [Bug c++/22139] [4.0/4.1 regression] Segfault with templates and friend functions mmitchel at gcc dot gnu dot org 2005-07-17 22:14 ` cvs-commit at gcc dot gnu dot org 2005-07-17 22:33 ` cvs-commit at gcc dot gnu dot org 2005-07-17 22:33 ` mmitchel at gcc dot gnu dot org 2005-07-31 5:17 ` pinskia at gcc dot gnu dot org
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=20050621234337.16135.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: 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).