From owner-freebsd-chromium@FreeBSD.ORG Fri Jun 8 13:06:27 2012 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 75D6E1065670 for ; Fri, 8 Jun 2012 13:06:26 +0000 (UTC) (envelope-from david@code.davidpcaldwell.com) Received: from mail-gg0-f182.google.com (mail-gg0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 286838FC0A for ; Fri, 8 Jun 2012 13:06:25 +0000 (UTC) Received: by ggnm2 with SMTP id m2so1400395ggn.13 for ; Fri, 08 Jun 2012 06:06:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=9nLIIg9ldngZ5+gzzXlIZYAFOooXhCKYXB5PTOlTEZs=; b=WStQAk4ZgX7xGKBupKdI3tQEJQ0rXi5LV5RRYS/BsfdVwcvYR82bp+vX0A4x+Chsi2 k5uPIq1lQhWiAYHqfvjnbPbzXJTHtVWBPM3lVnhBOS/Xw+UkJQ39SWVTPvngYxFUZOSe t/01A/SNTnTWOA1GKYezfvte3QgKOQCmIkfrUPjfgH9yvr9vuNgzS2sdvtOCveFo84O2 2U4r1xsZDZkqapk6UC6UOIIXeywTrlyBKgyUsgMxs4KJPZvRl/HdkytnL7USYkZYESLE iUaivDLxP7yjRv/nr6uCXGPz7oRZuv44pJFCB+IdQmKlGC0U8bR5bOs8WzHTKbCZGWkq JJ2Q== MIME-Version: 1.0 Received: by 10.50.10.164 with SMTP id j4mr2883409igb.13.1339160785098; Fri, 08 Jun 2012 06:06:25 -0700 (PDT) Received: by 10.64.70.165 with HTTP; Fri, 8 Jun 2012 06:06:25 -0700 (PDT) X-Originating-IP: [173.69.4.172] In-Reply-To: References: <20120607060457.GC98376@ithaqua.etoilebsd.net> Date: Fri, 8 Jun 2012 09:06:25 -0400 Message-ID: From: "David P. Caldwell" To: George Liaskos Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkE6plQcMdNJ4pJhPJ6HTbb+E+A61VMwRabCRONZ9leA2bVpW2hRwLB2YGdZlD61yV6DbHn Cc: freebsd-chromium@freebsd.org Subject: Re: Chromium 19 dumps core on 9.0-RELEASE (i386) X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2012 13:06:27 -0000 I don't know much about native libraries -- what would be the possible causes of a build with debugging symbols being functional but a build without them crashing? Is that a compiler bug? I built with gcc, if it's relevant. -- David. On Fri, Jun 8, 2012 at 8:11 AM, George Liaskos wrote: > On Fri, Jun 8, 2012 at 2:46 PM, David P. Caldwell > wrote: >> On Fri, Jun 8, 2012 at 3:46 AM, George Liaskos wrote: >>> On Thu, Jun 7, 2012 at 9:04 AM, Baptiste Daroussin wrote: >>>> On Wed, Jun 06, 2012 at 07:34:05PM -0400, David P. Caldwell wrote: >>>>> I built the latest Chromium 19 by building against the 9.0-RELEASE >>>>> *packages*. I did not want to update all my ports and incur the >>>>> various library problems that resulted the last time I tried that. I >>>>> may try it next. >>>>> >>>>> I am rebuilding with debug symbols, as when I tried to view >>>>> chrome.core in gdb, it just gave me a huge backtrace of "??" >>>>> instances. >>>>> >>>>> I had Chromium 18 running successfully with an older version of the >>>>> ports tree, built from source. But I can't reproduce that. >>>>> >>>>> I'm building inside a VirtualBox instance, if that makes any difference. >>>>> >>>>> I recognize this all may not be a very useful bug report, but I'm >>>>> still learning to file useful ones, so please bear with me. >>>>> _______________________________________________ >>>>> freebsd-chromium@freebsd.org mailing list >>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-chromium >>>>> To unsubscribe, send any mail to "freebsd-chromium-unsubscribe@freebsd.org" >>>> >>>> Confirmed, I got the same on my eeepc. >>>> >>>> regards, >>>> Bapt >>> >>> Debug build works for me under i386 vm, release crashes... I didn't >>> have enough time to debug this. >>> >>> Feedback is always welcome and needed. >>> >>> >>> Regards, >>> George >> >> What do you mean by "debug build" -- one with debug symbols enabled >> during make configure? >> >> I tried to build that and the build failed, and I gave up at that >> point, but I can keep trying. >> >> Of course, the reason I was trying to do the debug build was to find >> the problem, but are you saying that enabling the debug symbols >> somehow fixes the problem? >> >> -- David. > > Yes, with the debug option enabled chromium does not crash. It only > produces some error messages from the GPU thread about libGL being > old. > > Most probably you are running out of memory, that is why you cannot > finish the compile. I had to add swap.. even though my desktop has > 16GiB of ram they are not usable from the vm, i will try to recompile > the kernel with PAE.