SPARCworks C++ gets signal 11

SPARCworks C++ gets signal 11

Post by Steinar Ban » Wed, 05 Mar 1997 04:00:00



Platform: Solaris 2.5.1, UltraSPARC, SPARCworks C++ 4.1

Does the following error message ring a bell for anybody?

CC -I/opt/ospace/version-2 -I/opt/ospace/version-2/include -I/opt/ospace/version-2/ospace/std -I/opt/ODI/OS4.0.2/sunpro/include -I/real.fox/sb/source/2x/lib/gmlparser -I/real.fox/sb/source/2x/lib -I/real.fox/sb/source/2x/lib/orblib -I/real.fox/sb/source/2x/api/mpi -I/real.fox/sb/source/2x -I/opt/ODI/OS4.0.2/sunpro/include -I.. -g -DOS_SOLARIS_2_5 -DOS_STL_ASSERT -DOS_NO_WSTRING -DOS_USE_EXCEPTIONS -DOS_ANSI -DOS_PAGE_SIZE=128 -DSTL_TOOLKIT -DOSPACE_OSTORE -pta -vdelx -mt -c kcomplex.cpp    
 >> Signal 11:
    while processing kcomplex.cpp at line 3.
gmake: *** [kcomplex.o] Error 1

The first 4 lines of kcomplex.cpp, looks like this:
//-*- C++ -*-
/*
 *----------------------------------------------------------------------
 *

I'm assuming this is some kind of compiler bug, but I'm clueless as to
where to start looking for it.

So! Any hints/pointers appreciated!

Thanx!

- Steinar

--
===================<URL:http://www.metis.no/private/sb/>===================
Steinar Bang, NCR Norge AS, METIS ED&D, P.O.Box 1094, N-3194 Horten, Norway

 
 
 

SPARCworks C++ gets signal 11

Post by Steven Cart » Fri, 07 Mar 1997 04:00:00



Quote:>Platform: Solaris 2.5.1, UltraSPARC, SPARCworks C++ 4.1

>Does the following error message ring a bell for anybody?

[long line deleted]
> >> Signal 11:

I used to get signal 11's when I had memory that was too slow in the machine.
I only saw the problem on large compiles.  I upgraded the memory and the
problem went away.

Steven.

--
  Steven M. Carter                 .         "It's a damn poor mind that can
  Miss. State University / ._______|_______.  only think of one way to spell
  NSF Engr. Research Cntr.       \(*)/        a word."       -Andrew Jackson


 
 
 

SPARCworks C++ gets signal 11

Post by Ron Murp » Thu, 13 Mar 1997 04:00:00


Doesn't that happen when you run out of disk space?

Ron


>Platform: Solaris 2.5.1, UltraSPARC, SPARCworks C++ 4.1

>Does the following error message ring a bell for anybody?

>CC -I/opt/ospace/version-2 -I/opt/ospace/version-2/include -I/opt/ospace/version-2/ospace/std -I/opt/ODI/OS4.0.2/sunpro/include -I/real.fox/sb/source/2x/lib/gmlparser -I/real.fox/sb/source/2x/lib -I/real.fox/sb/source/2x/lib/orblib -I/real.fox/sb/source/2x/api/mpi -I/real.fox/sb/source/2x -I/opt/ODI/OS4.0.2/sunpro/include -I.. -g -DOS_SOLARIS_2_5 -DOS_STL_ASSERT -DOS_NO_WSTRING -DOS_USE_EXCEPTIONS -DOS_ANSI -DOS_PAGE_SIZE=128 -DSTL_TOOLKIT -DOSPACE_OSTORE -pta -vdelx -mt -c kcomplex.cpp
> >> Signal 11:
>    while processing kcomplex.cpp at line 3.
>gmake: *** [kcomplex.o] Error 1

>The first 4 lines of kcomplex.cpp, looks like this:
>//-*- C++ -*-
>/*
> *----------------------------------------------------------------------
> *

>I'm assuming this is some kind of compiler bug, but I'm clueless as to
>where to start looking for it.

>So! Any hints/pointers appreciated!

>Thanx!

>- Steinar

>--
>===================<URL:http://www.metis.no/private/sb/>===================
>Steinar Bang, NCR Norge AS, METIS ED&D, P.O.Box 1094, N-3194 Horten, Norway


--
Ron Murphy
U.S. Robotics
 
 
 

SPARCworks C++ gets signal 11

Post by Guy Harr » Thu, 13 Mar 1997 04:00:00



>Doesn't that happen when you run out of disk space?

It happens only to really crappily written programs.  Programs that do a
semi-decent job of checking for errors won't get a SIGSEGV (which is
what signal 11 is on most UNIXes) just because they ran out of disk
space (or out of *swap* space, for that matter - don't *EVER* assume
that "malloc()" can never return a NULL pointer!).
 
 
 

1. crashing Solaris C++ with signal 11

This fragment of code:

struct One {
  One();

struct Two {
  Two(One);

One a;

struct Three {
  Three(Two b = a);

crashes Solaris C++ (SC3.0.1) with this error message:

 >> Signal 11:
    while processing j.C at line 0.

The same error occurs if "struct" is replaced with "class" and "public:"
e.g.

class One {
public:
  One();

Can someone with a newer Solaris C++ tell me if the problem has been
corrected or not?

Thanks,

John Garnett
--
--
John Garnett

2. C <==> FORTRAN

3. HELP: Raplayer gets Signal 11 - can't get a core dump!

4. 320x200 modeline; DGA bug

5. Getting Signal 11 Fatal Error w/ GCC and Linux 1.0.9

6. Q: Transparent Button or Clickable Label - GTK or otherwise.

7. Seyon getting Killed by Signal 11 error

8. themes.org down?

9. pppd gets Fatal signal 11

10. if your GCC (or binutils) gets signal 11, READ THIS!

11. Why am I getting kill by signal 11...randomly

12. Can't compile console.c: gcc gets signal 11

13. SWI-Prolog gets unexpected signal 11