Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 20 Apr 2006 17:30:17 +0100
From:      David Reid <david@jetnet.co.uk>
To:        Joe Marcus Clarke <marcus@marcuscom.com>
Cc:        freebsd-gnome@freebsd.org
Subject:   Re: gnome 2.12 eog on amd64 crashes
Message-ID:  <4447B719.1010508@jetnet.co.uk>
In-Reply-To: <1145538900.28988.7.camel@shumai.marcuscom.com>
References:  <4447722A.7070106@jetnet.co.uk> <1145538900.28988.7.camel@shumai.marcuscom.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Joe Marcus Clarke wrote:
> On Thu, 2006-04-20 at 12:36 +0100, David Reid wrote:
>> I can't use eog on amd64 to open even a single image, let alone an
>> entire directory of them. What "bits" do I need to build as debug to get
>> a usable backtrace?
> 
> eog to start.

Rebuild eog with debug, ran it using

env GNOME_DISABLE_CRASH_DIALOG=1 eog

Got the trace below...

(gdb) bt
#0  0x00000008042a8eec in kse_thr_interrupt () from /lib/libpthread.so.2
#1  0x0000000804296750 in _thr_sig_dispatch () from /lib/libpthread.so.2
#2  0x00000008042a06ba in _kse_critical_leave () from /lib/libpthread.so.2
#3  0x0000000000000000 in ?? ()
Cannot access memory at address 0x7fffffbff000

Doesn't seem very helpful :-(

david



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4447B719.1010508>