On Thu, Feb 06, 2014 at 11:45:49AM -0500, Vince Weaver wrote: > > I'm running trinity compiled for x32 (by adding -mx32 to the CFLAGS > and -static in the LDFLGAS as for some reason my debian system with x32 > libs installed gives "FATAL: kernel too old" if I try to run the > dynamically linked version). > > Anyway I think glibc is reporting these particular errors. Should I try > tracking them down? Or is this normal when running trinity? > > Vince > > *** Error in `./trinity': corrupted double-linked list: 0x018c31f8 *** > *** Error in `./trinity': corrupted double-linked list: 0x01a68038 *** > *** Error in `./trinity': corrupted double-linked list: 0x0170a448 *** > *** Error in `./trinity': corrupted double-linked list: 0x01a0cd08 *** > *** Error in `./trinity': free(): invalid size: 0x01a150d0 *** I've spotted a bunch of weird stuff lately, like core dumps in odd places (when run with -D) (and gdb insisting it doesn't match the executable). I think it started when I added the mmap lists, but I've not nailed down exactly what's failing yet. I'm looking into it, but haven't got a good feel for what's going wrong. Dave -- To unsubscribe from this list: send the line "unsubscribe trinity" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
