[Bug c++/21670] segv after error
--- Additional Comments From reichelt at gcc dot gnu dot org 2005-05-24 14:20 --- Looks like it to me too, and I easily could have fallen into the same hole twice because it comes from a use of a shared library. Does a single fix make both go away? One never knows for sure until the patch is applied, but we already have two similar PRs (PR 20789, PR 20668), so chances are very high. Marking this as a duplicate then. *** This bug has been marked as a duplicate of 20789 *** -- What|Removed |Added Status|WAITING |RESOLVED Resolution||DUPLICATE http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21670
[Bug c++/21670] segv after error
--- Additional Comments From reichelt at gcc dot gnu dot org 2005-05-23 14:32 --- Ivan, this looks like a duplicate of your PR 20789 to me. Or is there any major difference? -- What|Removed |Added CC||reichelt at gcc dot gnu dot ||org Status|UNCONFIRMED |WAITING http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21670
[Bug c++/21670] segv after error
--- Additional Comments From igodard at pacbell dot net 2005-05-23 18:10 --- Looks like it to me too, and I easily could have fallen into the same hole twice because it comes from a use of a shared library. Does a single fix make both go away? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21670
[Bug c++/21670] segv after error
--- Additional Comments From igodard at pacbell dot net 2005-05-19 20:49 --- Created an attachment (id=8929) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8929action=view) compiler output -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21670
[Bug c++/21670] segv after error
--- Additional Comments From igodard at pacbell dot net 2005-05-19 20:50 --- Created an attachment (id=8930) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8930action=view) source code (compressed) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21670
