public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: blackkm@juno.com
To: gcc-gnats@gcc.gnu.org
Subject: c/7414: GCC 3.1 gens bad pointer arithmetic? SIGSEGV
Date: Fri, 26 Jul 2002 08:26:00 -0000	[thread overview]
Message-ID: <20020726151802.29944.qmail@sources.redhat.com> (raw)


>Number:         7414
>Category:       c
>Synopsis:       GCC 3.1 gens bad pointer arithmetic? SIGSEGV
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Fri Jul 26 08:26:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     K Black
>Release:        gcc version 3.1
>Organization:
>Environment:
Windows XP Home, Cygwin
>Description:
code appears to compile with no errors and no warnings.
But always produces SIGSEGV at run time
>How-To-Repeat:
Line 10 (/* fails here */) appears to always fail with a segmentation fault (SIGSEGV?)?

char *t[3]={
	"\0one",
	"\0two",
	"zzz"};

main() {

   printf("t[1] before: %s\n",t[1]);
   t[1][0]=' ';   /* fails here */
   printf("t[1] afterwords: %s\n",t[1]);
}
>Fix:
unknown - tried several variations on pointers and arrays
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-07-26 15:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-26  8:26 blackkm [this message]
2002-07-26 18:27 cgf

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=20020726151802.29944.qmail@sources.redhat.com \
    --to=blackkm@juno.com \
    --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).