Date: Sat, 28 Jun 2014 11:20:24 -0700 From: Eitan Adler <lists@eitanadler.com> To: The BSD Dreamer <beastie@tardisi.com> Cc: freebsd-chromium@freebsd.org Subject: Re: chrome fails with 'abort trap' Message-ID: <CAF6rxgm9oQ4Xdc7S3hjbt0QG_fF=Ld06=F75%2B%2BtnAH1fcw0mwA@mail.gmail.com> In-Reply-To: <3799c32ace539fa1989db0b48cb4dc7c@lhaven.homeip.net> References: <20140624120225.c50b1eb0df65195bc02b91d0@fbsd.es> <CAF6rxgmosacWfzC9ArYPzk4UwZH6OHvaNjswV6BH8uvn-MBxvA@mail.gmail.com> <3799c32ace539fa1989db0b48cb4dc7c@lhaven.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 28 June 2014 11:07, The BSD Dreamer <beastie@tardisi.com> wrote: > On 2014-06-24 14:43, Eitan Adler wrote: >> >> On 24 June 2014 03:02, Carlos Jacobo Puga Medina <cpm@fbsd.es> wrote: >>> >>> That's weird. Here [1] you've a similar problem related. >> >> >> This seems identical to my problem. >> >>> Have you built chrome with DEBUG enabled? >> >> >> Yes. Chrome was crashing without DEBUG enabled so I thought getting a >> backtrace would be useful. > > > I made that mistake as well, while trying to get any version since v33 of > chromium to > run on any of my systems. > > Meanwhile, I finally tracked down the culprit and I'm using > chromium-35.0.1916.153_1 to compose this message ;) > > The culprit was 'devel/libexecinfo' on amd64. > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191465 I wonder if we have different problems then? I was unable to repro this bug report. -- Eitan Adler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxgm9oQ4Xdc7S3hjbt0QG_fF=Ld06=F75%2B%2BtnAH1fcw0mwA>