From owner-freebsd-current  Thu Dec 10 09:30:05 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA18553
          for freebsd-current-outgoing; Thu, 10 Dec 1998 09:30:05 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns1.yes.no (ns1.yes.no [195.204.136.10])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18448;
          Thu, 10 Dec 1998 09:29:50 -0800 (PST)
          (envelope-from eivind@bitbox.follo.net)
Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218])
	by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id SAA22887;
	Thu, 10 Dec 1998 18:29:40 +0100 (CET)
Received: (from eivind@localhost)
	by bitbox.follo.net (8.8.8/8.8.6) id SAA01144;
	Thu, 10 Dec 1998 18:29:39 +0100 (MET)
Message-ID: <19981210182938.B371@follo.net>
Date: Thu, 10 Dec 1998 18:29:38 +0100
From: Eivind Eklund <eivind@yes.no>
To: vallo@matti.ee, current@FreeBSD.ORG
Cc: dg@FreeBSD.ORG
Subject: Re: mformat in free(): warning: junk pointer, too high to make sense.
References: <19981210174027.A4287@matti.ee>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <19981210174027.A4287@matti.ee>; from Vallo Kallaste on Thu, Dec 10, 1998 at 05:40:27PM +0200
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Dec 10, 1998 at 05:40:27PM +0200, Vallo Kallaste wrote:
> Hello !
> 
> I keep getting this error while trying to mformat one faulty floppy. 
> The procedure is:
> 
> myhakas# mformat a:
> plain_io: Input/output error
> Trouble initializing a FAT sector
> plain_io: Input/output error
> ^Cplain_io: Input/output error
> ^C^C^Cplain_io: Input/output error
> mformat in free(): warning: junk pointer, too high to make sense.
> mformat in free(): warning: junk pointer, too high to make sense.
> myhakas#
> 
> The event occurs while repeatedly hitting Ctrl-C. Can this be any 
> help to identify well known junk pointer thing ? Otherwise I leave 
> it, because it doesn't cause any other trouble. I run quite recent 
> current from Dec. 6. I haven't seen it before and I do lot of work 
> with dos-formatted floppies. I provide any other information if 
> needed.

It occur because mtools use non-signal-safe functions in its signal
handlers.  The 'best' thing to do would be to identify just what is done
wrong, and submit fixes back to the mtools maintainers.

As for the inetd problem:   We know what it is, we have a fix, and David
Greenman seems to be vetoing committing it due to its "inelegance".

Eivind.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message