public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rdhunt@sandia.gov
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/7111: cout of null pointer causes core dump
Date: Mon, 24 Jun 2002 15:35:00 -0000	[thread overview]
Message-ID: <20020624222023.14002.qmail@sources.redhat.com> (raw)


>Number:         7111
>Category:       libstdc++
>Synopsis:       cout of null pointer causes core dump
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jun 24 15:26:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     rdhunt@sandia.gov
>Release:        gcc version 3.1
>Organization:
>Environment:
Sun SunOS 5.8
>Description:
Trying to print a null character pointer causes this program to core dump.  This works fine under GCC 2.95.  I know null pointers are sensitive and am not completely sure if this is truly a bug or what the correct way of handling this is.
>How-To-Repeat:
Compile it and run it.  If I change the char* to be void* it works fine.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="checknull.cpp"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="checknull.cpp"

CiNpbmNsdWRlIDxpb3N0cmVhbS5oPgoKaW50IG1haW4oKQp7CiAgIGNoYXIgKm15bnVsbD1OVUxM
OwogICBjb3V0IDw8ICJteW51bGwgcmVzdWx0OiAiIDw8IG15bnVsbCA8PCBlbmRsOwp9Cg==


             reply	other threads:[~2002-06-24 22:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-24 15:35 rdhunt [this message]
2002-07-03 10:02 bkoz
2002-07-03 10:46 Phil Edwards
2002-07-04 10:01 bkoz

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=20020624222023.14002.qmail@sources.redhat.com \
    --to=rdhunt@sandia.gov \
    --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).