On Thu, 2011-06-16 at 22:51 +0200, Vincent Torri wrote:
>
> On Wed, 15 Jun 2011, Svante Signell wrote:
>
> > Hi, I'm compiling e17 on Debian GNU/Hurd and it compiles now with some
> > recent hurd/libc changes. However when starting it segfaults, seems to
> > be in the evas module. All EFL versions in Debian are 1.0.0. Is there
> > any known issue since then, now most libs are 1.0.1?
> >
> > I have a backtrace in case you are interested, see
> > http://paste.debian.net/119789/ How to best debug e17?
>
> for debugging e17:
>
> http://trac.enlightenment.org/e/wiki/Debugging
Thank you for your link to the debugging page. Attaching to the crashed
e17 enables you to get a bt from the crash, but not do single-stepping,
etc in gdb. However, I got a tip from Manuel Menal, who had e17 running
in GNU/Hurd some time ago.
In order to do single stepping in gdb you could do the following:
Start X with only an xterm xinit /usr/bin/xterm
Then run e17 from that xterm:
export E_START="enlightenment_start" ; gdb enlightenment
This worked for me an I found out that the crash happened at:
evas-1.0.0/src/lib/engines/common/evas_scale_sample.c:284
DATA32 *ptr, *dst_ptr, *src_data, *dst_data;
...
{
280: dst_ptr = dptr;
for (x = 0; x < dst_clip_w; x++) dst_clip_w = 36
{
ptr = row_ptr[y] + lin_ptr[x]; ptr= (DATA32 *) 0x8306bf8
284: *dst_ptr = *ptr; *ptr= 4284900966 <- crash here
dst_ptr++;
}
}
dptr += dst_w; *dptr= 4284900966
}
}
Are these pointer values reasonable? The seem very large to me.
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
