From owner-freebsd-questions  Wed Feb 14 12:13:46 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA10084
          for questions-outgoing; Wed, 14 Feb 1996 12:13:46 -0800 (PST)
Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA10079
          for <questions@freebsd.org>; Wed, 14 Feb 1996 12:13:44 -0800 (PST)
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id NAA27009; Wed, 14 Feb 1996 13:16:24 -0700
Date: Wed, 14 Feb 1996 13:16:24 -0700
From: Nate Williams <nate@sri.MT.net>
Message-Id: <199602142016.NAA27009@rocky.sri.MT.net>
To: kline@tera.com (Gary Kline)
Cc: questions@freebsd.org
Subject: Re: mktemp()
In-Reply-To: <9602141821.AA15933@tera.com>
References: <9602141821.AA15933@tera.com>
Sender: owner-questions@freebsd.org
Precedence: bulk

> The libc call mktemp() (along with strtok() and strsep(), by the way)
> causes a coredump when I use it with gcc.  This from v 2.0.5.  

Are you calling mktemp() with memory that is writeable?  By default,
strings are constants and un-writeable.

> On the Suns at work, strtok and strsep both bomb with gcc v2.3.3
> and both work with the standard Sun CC.  

Try adding -fwriteable-strings and I'll bet it will work.


Nate