Hi.

On 11/8/06, Steve Langasek <[EMAIL PROTECTED]> wrote:
reassign 397012 libimlib2
found 397012 1.3.0.0debian1-2
tags 397012 patch
thanks

> no, only png images.


Can you test with other images types (jpg or xpm).

Turns out I am able to reproduce this, I just misunderstood the symptoms
because something is trapping the segfault when not running under gdb and
idesk was therefore exiting silently instead of throwing an error message.

And I've tracked the problem down to some amd64 assembly code in
libImlib2.so.1:

#0  0x00002b9b2be201ff in __imlib_amd64_blend_rgba_to_rgb_cmod ()
   from /usr/lib/libImlib2.so.1
#1  0x00002b9b2bde8d14 in imlib_blend_image_onto_image (source_image=0x553800,
    merge_alpha=1 '\001', source_x=0, source_y=0, source_width=5593504,
    source_height=48, destination_x=0, destination_y=0,
    destination_width=48,
    destination_height=48) at api.c:2015
[...]

The instruction at 0x00002b9b2be201ff is:

0x00002b08934011ff <__imlib_amd64_blend_rgba_to_rgb_cmod+47>:   movdqa 
1155461(%rip),%xmm5      # 0x2b089351b38c <c1>


This sounds known. I think is related to PNG images.

I have no idea what this does, other than that it segfaults.  The easiest
fix I see is to simply disable the amd64 assembly in libimlib2 until someone
can take a look at and fix it; this can be done by adding a --disable-amd64

Ok, I'll think in that option if the bug is not fixed soon.

option to the configure command in debian/rules.  I've confirmed that doing
so fixes the segfault on my test system.


I built a special idesk package, just for test.

You can download it here:

http://fixxxer.cc/pub/idesk/idesk_0.7.5-3-debug-1_i386.deb

I removed  the dh_strip option and I added the libxt-dev dependency
due to the news changes on Xorg (it will be either 0.7.5-4 or 0.7.6-1,
I still don't know).

May be, it can be more descriptive for your test.

Regards.

--
Anibal Avelar (FixXxeR) http://fixxxer.cc
GPG: 83B64656 - C143 4AD8 B017 53FA B742  D6AA CEEA F9F3 83B6 4656


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to