exception bug shown by purify

Jack LENZ JLENZ@indocdv.com
Wed May 30 00:51:00 GMT 2001


Hi there,

While testing some exception stuff with gcc I came to a situation where I
used
purify. And purify signaled me an error that looks pretty much like a
compiler
error to me.

So here are the details.
- I'm running Solaris 2.5.1 on a sun sun4u sparc,  uname -a returns:
     SunOS padev010 5.5.1 Generic_103640-34 sun4u sparc SUNW,Ultra-5_10
- I'm using gcc version 2.95.2
- I compile with the command: g++ -o xxx tst.cc -g -Wall
- I've a downsized version of my original program that throws an exception;
  in this context purify (Purify 4.5.1 Solaris 2) detects a ZPR (zero page
  read).
- To operate the program you lunch it, and then enter 1 or 2 as input.
- I checked with the native sun CC compiler - no problem at all.
- Here is the output of my purify session:
****** START OF OUTPUT *************************
      ZPR: Zero page read
      This is occurring while in:
            add_fdes       [frame.c]
            __frame_state_for [frame.c:627]
            __throw        [libgcc2.c]
            proc()         [tst3.cc:50]
            main           [tst3.cc:70]
            _start         [crt1.o]
      Reading 4 bytes from 0x16
      COR: Fatal core dump
      This is occurring while in:
            add_fdes       [frame.c]
            __frame_state_for [frame.c:627]
            __throw        [libgcc2.c]
            proc()         [tst3.cc:50]
            main           [tst3.cc:70]
            _start         [crt1.o]
      Received signal 10 (SIGBUS - Bus Error)
      Faulting address = 0x16
      Signal mask: (SIGBUS)
      Pending signals:
****** END   OF OUTPUT *************************
- Please find the source code in the attached file.

Sincerely
Jack Lenz
home: jacklenz@freelenz.com
work: jlenz@indocdv.com

(See attached file: tst3.cc)
tst3.cc

-------------- next part --------------
A non-text attachment was scrubbed...
Name: tst3.cc
Type: text/x-c++
Size: 1041 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-bugs/attachments/20010530/6f5cdb88/attachment.bin>


More information about the Gcc-bugs mailing list