From owner-freebsd-chromium@FreeBSD.ORG Fri Jun 8 13:12:49 2012 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D1AD106566B; Fri, 8 Jun 2012 13:12:49 +0000 (UTC) (envelope-from geo.liaskos@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0A6048FC14; Fri, 8 Jun 2012 13:12:48 +0000 (UTC) Received: by qcsg15 with SMTP id g15so1005945qcs.13 for ; Fri, 08 Jun 2012 06:12:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Dl+MKCvzwaNOh8wGbSdtOESw0A4vkNC1Y+6yGEaOFb8=; b=w84hdUPw92XEzV2J7lsPQuVuF+UeiuW8rPY2IGdoRj7bluRO7Wgvs94/SRRjsAR/Gg jjAKO4uL+1+wft0G8kTpsngot3iaSbuJXuG3VN5morswH+mViEzC7P0RfSefWN5XsYoR 77iOGhuSKy2I1y7e7fYf4DairkhlspX6pZW/uO5FG4I7tOvKPqIoNBwajXkT00PMX36l IiaKWUU2GJ/EW45XD7L4XaRKClFO9g3JqknfT39/aywa1BSQA8X/7P8vSBwVp+vbiRNP i/q7pkvcn1iXUNwsx2mJyqJS5Wz42EBST6+WWaF2m/qxGzh6zHhPqKglHKoh1cMOL25l +24w== MIME-Version: 1.0 Received: by 10.224.78.81 with SMTP id j17mr6997790qak.43.1339161168308; Fri, 08 Jun 2012 06:12:48 -0700 (PDT) Received: by 10.229.155.2 with HTTP; Fri, 8 Jun 2012 06:12:48 -0700 (PDT) In-Reply-To: References: <20120607060457.GC98376@ithaqua.etoilebsd.net> Date: Fri, 8 Jun 2012 16:12:48 +0300 Message-ID: From: George Liaskos To: "David P. Caldwell" Content-Type: text/plain; charset=UTF-8 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:12:49 -0000 On Fri, Jun 8, 2012 at 4:06 PM, David P. Caldwell wrote: > 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. Wild guess, it could be a macro using NDEBUG to abort.