public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: steven@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	ocmbah@unity.ncsu.edu
Subject: Re: c/9857: string tokenizer causes segmentation faults
Date: Wed, 26 Feb 2003 13:23:00 -0000	[thread overview]
Message-ID: <20030226132303.29800.qmail@sources.redhat.com> (raw)

Synopsis: string tokenizer causes segmentation faults

State-Changed-From-To: open->closed
State-Changed-By: steven
State-Changed-When: Wed Feb 26 13:23:02 2003
State-Changed-Why:
    This is not a compiler bug.  You can't use strtok on constant strings.  See the manpages. (Note that those also say: "Never use these functions.")

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9857


             reply	other threads:[~2003-02-26 13:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-26 13:23 steven [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-26  5:46 ocmbah

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=20030226132303.29800.qmail@sources.redhat.com \
    --to=steven@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=ocmbah@unity.ncsu.edu \
    /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).