From owner-freebsd-chromium@FreeBSD.ORG Fri Jun 8 11:47:17 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 91B53106566B for ; Fri, 8 Jun 2012 11:47:17 +0000 (UTC) (envelope-from david@code.davidpcaldwell.com) Received: from mail-gh0-f182.google.com (mail-gh0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 475CA8FC08 for ; Fri, 8 Jun 2012 11:47:17 +0000 (UTC) Received: by ghbz22 with SMTP id z22so1322628ghb.13 for ; Fri, 08 Jun 2012 04:47:11 -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=+QGQ9vzv4YHNEPKglPUevpkDfYqi0ya54At1v6Z/CEM=; b=l8e6k8zmtuisEMYG7d31Q6w9qYzUED3ZfGZOEiv1y6G/5qLrkJRANs+zi9dsVpHsG8 5kIsjrcPJstMN0G1k35uOPSNHt5/r8AQJ6mmObBNlSZDO+inz3iehG0u+DjNhjZ0Ic4G NzrSZE4WX1NTzUPGR0pZ4MZdGXY1WfvuOPMqgmWIlj1Va3E0PTtOOQ0s+BJC+QZlmPDF kiA/OhgHTAajw2c2Lgwib5vIhXucp3H9zUK8Dk9QIrub/gz5Mg634Sto5WeRbeuu3xQ2 o4v7vs5XKEFchLJllUeck2mYujvPR1pINcgOSg5+fCvxzX/BITkj04xQD6s27ec10idg QIlA== MIME-Version: 1.0 Received: by 10.50.41.165 with SMTP id g5mr2774044igl.13.1339156018394; Fri, 08 Jun 2012 04:46:58 -0700 (PDT) Received: by 10.64.70.165 with HTTP; Fri, 8 Jun 2012 04:46:58 -0700 (PDT) X-Originating-IP: [70.164.246.115] In-Reply-To: References: <20120607060457.GC98376@ithaqua.etoilebsd.net> Date: Fri, 8 Jun 2012 07:46:58 -0400 Message-ID: From: "David P. Caldwell" To: George Liaskos Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkIOJEY+0x7EPrTtK/5Y8+g7HW7p2OMZUDkWLpt0+Lx9wMhghcmONFT6uNvtpOG/yPGs2X2 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 11:47:17 -0000 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.