Control: retitle 764076 cross-version xdotool+libxdo crash on i386
Control: tags 764076 - unreproducible
Control: tags 764076 + help

On 10/06/2014 09:05 AM, Jakub Wilk wrote:
> * Daniel Kahn Gillmor <[email protected]>, 2014-10-06, 08:34:
>> 0 dkg@alice:~$ uname -a
>> Linux alice 3.14-2-amd64 #1 SMP Debian 3.14.15-2 (2014-08-09) x86_64
>> GNU/Linux
>> 0 dkg@alice:~$ dpkg-query -W libxdo3 xdotool
>> libxdo3    1:3.20140805.1-1
>> xdotool    1:3.20130111.1-5
>> 0 dkg@alice:~$ xdotool sleep 0
>> 0 dkg@alice:~$
> 
> I think it's architecture that makes the difference. I can reproduce the
> bug on i386, but not on amd64.
> 
> Backtrace:
> #0  0xf7ce0ddc in __GI_raise (sig=sig@entry=6) at
> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> #1  0xf7ce2463 in __GI_abort () at abort.c:89
> #2  0xf7d1fb88 in __libc_message (do_abort=do_abort@entry=1,
> fmt=fmt@entry=0xf7de39fc "*** Error in `%s': %s: 0x%s ***\n") at
> ../sysdeps/posix/libc_fatal.c:175
> #3  0xf7d25c03 in malloc_printerr (action=<optimized out>,
> str=0xf7ddfd72 "free(): invalid pointer", ptr=0x8066b28) at malloc.c:4996
> #4  0xf7d2685d in _int_free (av=0xf7e21400 <main_arena>, p=<optimized
> out>, have_lock=0) at malloc.c:3840
> #5  0xf7c1bed2 in XextRemoveDisplay (extinfo=0xf7cac124
> <_xtest_info_data>, dpy=dpy@entry=0x805a020) at ../../src/extutil.c:208
> #6  0xf7ca8b25 in close_display (dpy=0x805a020, codes=0x8066b44) at
> ../../src/XTest.c:88
> #7  0xf7e44591 in XCloseDisplay () from /usr/lib/i386-linux-gnu/libX11.so.6
> #8  0xf7fc8939 in xdo_free (xdo=0x8066af8) at xdo.c:146
> #9  0x0804acb0 in args_main (argc=2, argv=0xffffd788) at xdotool.c:511
> #10 0x0804a5a5 in xdotool_main (argc=3, argv=0xffffd784) at xdotool.c:316
> #11 0x0804a4bc in main (argc=3, argv=0xffffd784) at xdotool.c:287

thanks, i can confirm this on i386 as well.

It's very peculiar, because the sequence of library calls is identical,
whether i'm running the jessie or sid version of xdotool.

It's tempting to close this bug by forcing an exact match between
versions of xdotool and libxdo, but I'm concerned that the problem is
something in the underlying X11 libraries, and closing the bug this way
might just paper over the problem.

Any suggestions for how to get to the cause of this?

        --dkg

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to