On Tue, 26 Dec 2006, Shawn Pearce wrote: > > I'm suspecting this is actually some sort of memory corruption in > the heap (due to a bad malloc/free) as the bug seems to rear its > head only based on the data we are allocating/have allocated. Can you try to reproduce it under Linux and use "valgrind" to run the thing that SIGSEGV's? That tends to be a pretty good way to debug bad allocations.. So instead of bisecting it on cygwin, try to use the build that broke on Linux too (ie undo the 5caf9232 "fix") and when you can reproduce it under Linux, compiel withour -O2 and with debug information, and gdb will be a lot more useful, but also run it with valgrind.. Linus - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html