From owner-freebsd-current Fri Sep 22 16:34:30 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA28491 for current-outgoing; Fri, 22 Sep 1995 16:34:30 -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 QAA28473 for ; Fri, 22 Sep 1995 16:34:19 -0700 Received: by main.statsci.com (Smail3.1.29.1 #3) id m0swHbS-000r3tC; Fri, 22 Sep 95 16:33 PDT Message-Id: X-Mailer: exmh version 1.6.1 5/23/95 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: rich@lamprey.utmb.edu, 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 22:48:05 +0200." <199509222048.WAA10420@uriah.heep.sax.de> Reply-to: scott@statsci.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 22 Sep 1995 16:33:36 -0700 From: Scott Blachowicz Sender: owner-current@freebsd.org Precedence: bulk J Wunsch wrote: > As Scott Blachowicz wrote: > > > > 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? > > On which server? This is all standalone on my home PC - So the answer would be, I guess, the 3.1.1 (u1?) XF86_Mach64 server. > Try running xrdb without cpp. I'll try that (or would upgrading to 3.1.2 possibly solve the problem too?). Thanx, 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