Hi dann, sorry for letting this sleep for so long :(
On Wed, Feb 06, 2008 at 06:00:13PM -0700, dann frazier wrote: > #0 _int_malloc (av=0x20000000006a9148, bytes=24) at malloc.c:4139 > p = <value optimized out> > nb = 32 > idx = 2 > bin = (mbinptr) 0x20000000006a91b8 > victim = (mchunkptr) 0x6000000000178a70 > size = <value optimized out> > victim_index = <value optimized out> > remainder = <value optimized out> > remainder_size = <value optimized out> > block = <value optimized out> > bit = <value optimized out> > map = <value optimized out> > fwd = <value optimized out> > bck = (mchunkptr) 0x0 > #1 0x2000000000520df0 in *__GI___libc_malloc (bytes=24) at malloc.c:3553 > ar_ptr = (mstate) 0x20000000006a9148 > victim = (void *) 0x20000000006a9148 > hook = <value optimized out> > #2 0x40000000003588d0 in LogVMessageVerb (type=X_INFO, verb=3, > format=0x400000000036b538 "Bus %s I/O range:\n", args=0x60000fffffefb3c8) > at ../../os/log.c:362 > s = 0x400000000037adb8 "(II)" > tmpBuf = <value optimized out> This is weird... Either glibc is broken, or we have corrupted the heap. On x86 I'd suggest to run X under valgrind, but I don't know how to debug this on ia64 :/ Cheers, Julien -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
