[darcs-devel] darcs patch: Libwww new API: waitUrl, copyUrlFirst added; copyUrls ...

[zooko]

> Argh! A heisenbug.  When I set ulimit -c unlimited, I don't get the
> segfault (which otherwise is completely reproducible).

This is almost certainly a coincidence -- the setting of your ulimit  
can almost certainly not effect the behavior of your program.

> If I run under
> valgrind, I don't get a segfault.

I would be very surprised if you had a program with memory management  
errors, and you ran it under valgrind, and valgrind didn't print out  
a warning showing you precisely where memory was being accessed  
incorrectly -- even if the program didn't crash.  What did valgrind  
emit when you tried this?

Regards,

Zooko