From owner-freebsd-gecko@FreeBSD.ORG Sun Jun 1 23:30:16 2014 Return-Path: Delivered-To: gecko@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EE5708D2; Sun, 1 Jun 2014 23:30:16 +0000 (UTC) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id D336E2E2C; Sun, 1 Jun 2014 23:30:16 +0000 (UTC) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 7D78D3AE46; Sun, 1 Jun 2014 16:20:24 -0700 (PDT) From: "Ronald F. Guilmette" To: Kevin Oberman , gecko@FreeBSD.org, freebsd-ports@freebsd.org Subject: Two questions about Firefox Date: Sun, 01 Jun 2014 16:20:24 -0700 Message-ID: <3709.1401664824@server1.tristatelogic.com> X-BeenThere: freebsd-gecko@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Gecko Rendering Engine issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jun 2014 23:30:17 -0000 1) Is anybody planning to work on this problem? http://www.freebsd.org/cgi/query-pr.cgi?pr=189991 2) How has it been possible to fix other problems in the FreeBSD port of Firefox if nobody is even able to run the thing when it has been built with debugging enabled? (May I safely infer that _nobody_ is _ever_ working to fix any bugs found in Firefox on FreeBSD? The fact that the thing cannot even be run with debugging enabled would seem to lead one to that conclusion.)