From owner-freebsd-chromium@FreeBSD.ORG Wed Jun 6 23:34:07 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 16226106564A for ; Wed, 6 Jun 2012 23:34:07 +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 C66998FC17 for ; Wed, 6 Jun 2012 23:34:06 +0000 (UTC) Received: by ggnm2 with SMTP id m2so6023ggn.13 for ; Wed, 06 Jun 2012 16:34:06 -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:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=7hqiRuO4lAuhvLEwqhVRB7xWf5HIEoJ+3F5YNkTfNCM=; b=FvmkG9cP7Sccdj5xpu5cjR6sMNq3p5tBjIj2IwdFAziAQhDPSDcHM2Jvsk6BffE5C5 Ht3rqPeDEh8gHBqy5Y430oUj3Ljo3A3qZsFzRsmZXDkBEnBL9OnWX1PoxasTvDi4bLF8 SPhE4bI8PROH0YVg6eGg6xMXFP/EGHTUktHFDa8CORpZfCaP5stUJ69+iZSSt4+zkqY9 uTNZQ6n5EhhP7wkZmSWhhDucWQSPRqch1ubFWwkUz6X6vQtwHPTilrb6wm73qqQUqwJx e7w2XmfoW75qzPKN85YBB+3K/0rEHiBp4CowZf8SMtW1p0XPc1Lof3HXltu05jAlcVMU 99oA== MIME-Version: 1.0 Received: by 10.42.130.68 with SMTP id u4mr9495ics.17.1339025645647; Wed, 06 Jun 2012 16:34:05 -0700 (PDT) Received: by 10.64.133.198 with HTTP; Wed, 6 Jun 2012 16:34:05 -0700 (PDT) X-Originating-IP: [173.69.4.172] Date: Wed, 6 Jun 2012 19:34:05 -0400 Message-ID: From: "David P. Caldwell" To: freebsd-chromium@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQmcJQXHB6xzlWRgZw1CJkJ4526HEo1noIrbFfhlyjXim2jGfKYIXdCYvLGGqjDuesUDNq7d Subject: 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: Wed, 06 Jun 2012 23:34:07 -0000 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.