On Fri, May 14, 2010 at 10:22:53AM -0400, Matthew Craig wrote:

process limits set in your environmen (ulimit -a)

mtc@freedomincluded:~$ ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 4019 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 4019 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited

Ok, so that's not it... Do you get a core file when it aborts? If so please run gdb on it: gdb <path to dillo binary> <path to core file> and type "bt" at the gdb prompt. The output might give us a hint on what's failing.