From owner-freebsd-bugs  Mon May 12 02:26:24 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id CAA08058
          for bugs-outgoing; Mon, 12 May 1997 02:26:24 -0700 (PDT)
Received: from tfs.com (tfs.com [140.145.250.1])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id CAA08053
          for <bugs@FreeBSD.ORG>; Mon, 12 May 1997 02:26:22 -0700 (PDT)
Received: from critter.dk.tfs.com by tfs.com (smail3.1.28.1) with SMTP
	id m0wQrMc-0003xWC; Mon, 12 May 97 02:25 PDT
Received: from critter (localhost [127.0.0.1])
	by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id LAA02393;
	Mon, 12 May 1997 11:24:26 +0200 (CEST)
To: joerg_wunsch@interface-business.de (Joerg Wunsch)
cc: bugs@FreeBSD.ORG
From: Poul-Henning Kamp <phk@dk.tfs.com>
Subject: Re: malloc(): recursive call 
In-reply-to: Your message of "Mon, 12 May 1997 10:16:48 +0200."
             <19970512101647.UD18700@ida.interface-business.de> 
Date: Mon, 12 May 1997 11:24:26 +0200
Message-ID: <2391.863429066@critter>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

In message <19970512101647.UD18700@ida.interface-business.de>, J Wunsch writes:

>mail in malloc(): error: recursive call.
>Abort trap - core dumped
>
>Anybody ever seen such?

Yes, usually means that a signal handler tried to malloc(), despite the
fact that the signal happened inside malloc's implementation.

Could be something as simple as a fprintf :-(

--
Poul-Henning Kamp           | phk@FreeBSD.ORG       FreeBSD Core-team.
http://www.freebsd.org/~phk | phk@login.dknet.dk    Private mailbox.
whois: [PHK]                | phk@tfs.com           TRW Financial Systems, Inc.
Power and ignorance is a disgusting cocktail.