Article View: gnu.g++.bug
Article #873Re: fatal signal in g++-2.2.2
From: Vance Maverick
Date: Tue, 01 Sep 1992 17:09
Date: Tue, 01 Sep 1992 17:09
11 lines
759 bytes
759 bytes
This fatal signal, like the one I reported yesterday, went away when I
fixed a logical error. The "new Note" statement was the locus of the
problem, which was fixed by adding a conventional copy constructor to
the Identifier class, viz.
Identifier(const Identifier &other) {
str = other.str;
}
Hope this helps,
Vance
Technical Details
Message-ID:
<9209011709.AA09022@mahogany.CS.Berkeley.EDU>Path:
arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!mahogany.cs.berkeley.edu!maverickShow Full Headers
Complete Article Headers
Newsgroups: gnu.g++.bug Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!mahogany.cs.berkeley.edu!maverick From: maverick@mahogany.cs.berkeley.edu (Vance Maverick) Subject: Re: fatal signal in g++-2.2.2 Message-ID: <9209011709.AA09022@mahogany.CS.Berkeley.EDU> Sender: gnulists@ai.mit.edu Organization: GNUs Not Usenet Distribution: gnu Date: Tue, 1 Sep 1992 17:09:11 GMT Approved: bug-g++@prep.ai.mit.edu Lines: 12