"Anthony Tiemens" <[EMAIL PROTECTED]> writes: >>>>>>>>>HERE'S MY BACKTRACE... > (gdb) ba > #0 0x125b8 in xalloc_die+0x18 () > #1 0x19244 in xnrealloc_inline+0x7c () > #2 0x19298 in xrealloc+0x30 () > #3 0x193e0 in x2nrealloc_inline+0xd0 () > #4 0x19430 in x2realloc+0x30 () > #5 0xd4b4 in fillbuf+0x55c () > #6 0xf560 in mergefps+0x748 () > #7 0x1036c in merge+0xa4 () > #8 0x10920 in sort+0x3b0 () > #9 0x12224 in main+0x131c ()
That provides a bit of information, but it's not enough to tell us what the problem is. Can you please have your correspondent rebuild 'sort' using the -g option, so that we can debug it better? In the meantime, you might try running 'sort' using 'valgrind', if you can. Perhaps that will catch a memory-related problem. Does the input file contain very long lines? _______________________________________________ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
