From owner-freebsd-hackers  Tue Apr  2 21:51:16 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id VAA16347
          for hackers-outgoing; Tue, 2 Apr 1996 21:51:16 -0800 (PST)
Received: from tfs.com (tfs.com [140.145.250.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA16342
          for <hackers@freebsd.org>; Tue, 2 Apr 1996 21:51:14 -0800 (PST)
Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP
	id m0u4LTH-0003w4C; Tue, 2 Apr 96 21:51 PST
Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id FAA01926; Wed, 3 Apr 1996 05:51:05 GMT
X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol
To: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
cc: hackers@freebsd.org
Subject: Re: phkmalloc and buggy sw... 
In-reply-to: Your message of "Tue, 02 Apr 1996 21:14:41 +0200."
             <199604021914.VAA26438@labinfo.iet.unipi.it> 
Date: Wed, 03 Apr 1996 05:51:03 +0000
Message-ID: <1924.828510663@critter.tfs.com>
From: Poul-Henning Kamp <phk@critter.tfs.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> It happened to me twice now... I have some software which intermixes
> printf() and putchar(), and since the switch to phkmalloc it coredumps
> at times on the putchar() call.
> 
> Just for the records... I can't tell if there is something terribly
> wrong in my program or it is putchar which must be fixed. I solve the
> problem by replacing putchar('\n') with printf("\n"), and it doesn't
> coredump anymore.

Send it to me please, we may have a libc error.

--
Poul-Henning Kamp           | phk@FreeBSD.ORG       FreeBSD Core-team.
http://www.freebsd.org/~phk | phk@login.dknet.dk    Private mailbox.
whois: [PHK]                | phk@ref.tfs.com       TRW Financial Systems, Inc.
Future will arrive by its own means, progress not so.