From owner-freebsd-current Fri Sep 22 09:52:05 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA09950 for current-outgoing; Fri, 22 Sep 1995 09:52:05 -0700 Received: from main.statsci.com (main.statsci.com [198.145.127.110]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id JAA09945 for ; Fri, 22 Sep 1995 09:52:02 -0700 Received: by main.statsci.com (Smail3.1.29.1 #3) id m0swBH8-000r3uC; Fri, 22 Sep 95 09:48 PDT Message-Id: X-Mailer: exmh version 1.6.1 5/23/95 To: rich@lamprey.utmb.edu cc: bde@zeta.org.au, freebsd-current@freebsd.org, roberto@keltia.Freenix.FR Subject: Re: XFree86 and the new malloc In-reply-to: Your message of "Fri, 22 Sep 1995 10:33:00 -0500." <199509221533.KAA04960@id.slip.bcm.tmc.edu> Reply-to: scott@statsci.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 22 Sep 1995 09:48:15 -0700 From: Scott Blachowicz Sender: owner-current@freebsd.org Precedence: bulk > |FreeBSD-2.0.5 only has Xfree 3.1.1. I don't use X much, and 3.2.2 doesn't > |work here (*), so I just use the version of the cdrom. Would any of this talk of mallocs explain why I get segmentation violations out of xrdb on a stock 2.0.5R/XFree 3.1.1 form CD system? Or should I investigate a bit more? Scott Blachowicz Ph: 206/283-8802x240 StatSci, a div of MathSoft, Inc. 1700 Westlake Ave N #500 scott@statsci.com Seattle, WA USA 98109 Scott.Blachowicz@seaslug.org