public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: tonyhoyt@optonline.net
To: gcc-gnats@gcc.gnu.org
Subject: c/2748: Solaris, pointers and accessing memory with them.
Date: Sat, 05 May 2001 16:06:00 -0000	[thread overview]
Message-ID: <20010505225645.8579.qmail@sourceware.cygnus.com> (raw)

>Number:         2748
>Category:       c
>Synopsis:       Solaris, pointers and accessing memory with them.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat May 05 16:06:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Tony Hoyt
>Release:        gcc version 2.95.3 20010315 (release)
>Organization:
>Environment:
sparc-sun-solaris2.7
>Description:
 This example is intended to show a bug in Gcc for solaris.
I'm not good at explaining exactly what happens since I'm
poor with proper programming terms. I'm not sure if it's a 
casting problem, maping problem or a delcaration issue. 
All I know is that the INCREMENTED_POINTER version of this
application crashes on my Ultra 1 and Ultra 2 Solaris Boxes.
   
  I've tried this with GCC 2.95.3 and Sun Workshop 5.0. 
Both on Solaris 7 systems with all the latest patches
from Sun.
   
  I do know that the code does seem to work on linux. But,
I have not tried it else where.
>How-To-Repeat:
compile the above application and simply let it run.  It should crash with a bus error on a Solaris box with 2.95.3.  At least it does for me. If you want the original source, let me know.  
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-05-05 16:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-05 16:06 tonyhoyt [this message]
2002-03-02 20:36 rodrigc
2002-08-23 12:46 jsm28

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=20010505225645.8579.qmail@sourceware.cygnus.com \
    --to=tonyhoyt@optonline.net \
    --cc=gcc-gnats@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: link
Be 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).