From owner-freebsd-chromium@FreeBSD.ORG Mon Apr 11 16:01:16 2011 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 017B9106564A for ; Mon, 11 Apr 2011 16:01:16 +0000 (UTC) (envelope-from andrewwtulloch@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id AB3778FC08 for ; Mon, 11 Apr 2011 16:01:15 +0000 (UTC) Received: by vxc34 with SMTP id 34so5265452vxc.13 for ; Mon, 11 Apr 2011 09:01:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:date:x-google-sender-auth :message-id:subject:from:to:content-type; bh=IAMXM8cioSagjtJQcL+ecDqAFd1sgyH/uZIundvODN0=; b=Qjo2jwDMDkHwuoUpyAN6hFmdrMsI+Nee3IjsnY/VFZ7PyFUr2aLI+YDSat/c/2vrRK SEcK7nqRO9soROgBK2xi5dQfVuI3CHAUyjULBNMajmOZsC/RncAu+PS78VT6rusT/2MP IOqUCaXOqtAE/5csj6JHilbVmMKQPusayC5jw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=HCv6vSLr8gItSwwqtRaOXciZp00b+hqxjom9rtb4/aKkxdNJ6R405pJ+DPi+uWdaGE 8fyWnihiErKw3JDUwlHIKpdlA6f0lX/5YGv7Ygs2boEgNrwPoOXv41yVDLY120ScS5Ia 09b+dzuo6t/jnI3tl7irc3qZHRQF+P3AASJCc= MIME-Version: 1.0 Received: by 10.220.188.11 with SMTP id cy11mr421333vcb.11.1302535858575; Mon, 11 Apr 2011 08:30:58 -0700 (PDT) Sender: andrewwtulloch@gmail.com Received: by 10.220.84.76 with HTTP; Mon, 11 Apr 2011 08:30:58 -0700 (PDT) Date: Mon, 11 Apr 2011 16:30:58 +0100 X-Google-Sender-Auth: pV7efk_h41zs9sENNe6AhNXCT9w Message-ID: From: Andrew To: freebsd-chromium@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: 10.0.648.204 port doen't work on FreeBSD 8.2-STABLE 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: Mon, 11 Apr 2011 16:01:16 -0000 I've got a 8.2-STABLE amd64 desktop with 12GB ram so I could test debug builds, are there any tips for debugging chromium? I've also noticed there's been quite a bit of work in HEAD around threading, so perhaps the reason for the failure on 8.x lies there as there seems to be mention of process shared mutex, which I'm guessing is what we're talking about for multi-process chromium. Oddly I've tried running chrome --renderer-cmd-prefix='xterm -e gdb72 --eval-command=run --args' and it seems to work correctly. When I try running without gdb I hit: [0411/162832:FATAL:condition_variable_posix.cc(36)] Check failed: rv == 0. Unable to get symbols for backtrace. Dumping raw addresses in trace: 0x1276099 0x12b31ac 0x12b50a2 0x12b50d9 0x12bfc9f 0x2c353b6 0x10ba0bf 0x10b9487 0x11023bb 0x54389c 0x543048 0x5444f2 0x54489b 0x542e2e