public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org To: despriee@free.fr, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, mathieu.despriee@transatel.com, nobody@gcc.gnu.org Subject: Re: c++/5493: G++ 3.0.2 segmentation fault Date: Sun, 27 Jan 2002 11:44:00 -0000 [thread overview] Message-ID: <20020127194438.4763.qmail@sources.redhat.com> (raw) Synopsis: G++ 3.0.2 segmentation fault State-Changed-From-To: open->closed State-Changed-By: rodrigc State-Changed-When: Sun Jan 27 11:44:38 2002 State-Changed-Why: The error message produced said to contact qa.mandrakesoft.com. Did you do that? I could reproduce your problem with the FSF version of gcc 3.0.3. With FSF version of gcc 3.1 in CVS, I did not get a compiler seg fault, but got the following errors: ============================================================== In file included from ESmsV2Crypto.h:5, from testage.c++:36: BinaryArray.h: In constructor `BinaryArray<maxSize>::BinaryArray()': BinaryArray.h:71: class `BinaryArray<maxSize>' does not have any field named ` template<class _Tp> class std::valarray' BinaryArray.h: In constructor `BinaryArray<maxSize>::BinaryArray(const char*)': BinaryArray.h:77: class `BinaryArray<maxSize>' does not have any field named ` template<class _Tp> class std::valarray' BinaryArray.h: In copy constructor `BinaryArray<maxSize>::BinaryArray(const BinaryArray<maxSize>&)': BinaryArray.h:86: class `BinaryArray<maxSize>' does not have any field named ` template<class _Tp> class std::valarray' In file included from testage.c++:36: ESmsV2Crypto.h: At global scope: ESmsV2Crypto.h:20: `ESmsV2' was not declared in this scope ESmsV2Crypto.h:20: parse error before `)' token ===================================================================== The following fixes your code, and compiles with gcc 3.0.3 and gcc 3.1 in CVS: =========================================================== --- old.ii Sun Jan 27 14:42:01 2002 +++ preprocessed.source.ii Sun Jan 27 14:37:05 2002 @@ -37952,13 +37952,13 @@ template <uint maxSize> inline BinaryArray<maxSize>::BinaryArray() : - std::valarray(0, maxSize) + std::valarray<uchar>(maxSize) { } template <uint maxSize> inline BinaryArray<maxSize>::BinaryArray(const char* array) : - std::valarray(maxSize) + std::valarray<uchar>(array, maxSize) { for(uint i=0; i<maxSize; i++) (*this)[i] = array[i]; @@ -37967,7 +37967,7 @@ template <uint maxSize> inline BinaryArray<maxSize>::BinaryArray(const BinaryArray<maxSize>& right) : - std::valarray(right) + std::valarray<uchar>(right, maxsize) { } template <uint maxSize> @@ -38068,7 +38068,7 @@ { public: static KappKey getKappKey(uint kappKeyId); - static void compute(ESmsV2*); + static void compute(ESmsV2Crypto*); private: static void decryptKey(KappKey&); http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5493
next reply other threads:[~2002-01-27 19:44 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-27 11:44 rodrigc [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-01-25 10:46 mathieu.despriee
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=20020127194438.4763.qmail@sources.redhat.com \ --to=rodrigc@gcc.gnu.org \ --cc=despriee@free.fr \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=mathieu.despriee@transatel.com \ --cc=nobody@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).