CodeSourcery + Cygwin1.7 + Windows 7 = BSOD?

[Tom Evans]

I'm developing code for a Coldfire CPU.

Part of the build requires external tools to manipulate video files, 
build fonts and to "package" the binary into the shippable load format. 
We also need to copy files around. In other words we want to write 
Makefiles as if we were running on Linux. But one of the tools only runs 
under Windows so we have to use the MINGW port of CodeSourcery instead 
of the Linux one.

So we are running "cs-make" calling the m68k-elf-gcc-4.3.3 compiler 
under Cygwin 1.7.

This works on all the Win-XP machines and VMs at work without any 
problems, but that combination BSODs my Windows 7 dual core laptop in 
seconds. Big fatal Blue-Screen STOPs.

Applications aren't meant to be able to BSOD an operating system, but 
this mix does. It even BSODs the machine in console-only SAFE mode!

It works perfectly with Cygwin 1.5, but not 1.7. It seems to work if I 
run the compiler under cygwin's "make" instead of cs-make (but there are 
unresolvable "/" and "\" path problems with that mix).

I've had BSODs 0x01, 0x19, 0x24, 0x8e and others. Basically "Kernel 
memory is getting corrupted".

Is there anything about Cygwin and Mingw that could explain these? Is 
this a known bad mix?

Or is the best guess that the laptop has buggy chip and device drivers 
that this mix and load are tripping up?

Any suggestions on debugging Windows BSODs welcome. I've dropped the 
mini-dumps on WinDbg, but it doesn't help much.

-- 
=========
Tom Evans
thomasaevans at optusnet.com.au   - Home - preferred
thomasalexanderevans at gmail.com - Home
tom.evans at motec.com.au         - Work

+61 (3) 9857-8805 - Home
+61 (3) 9761-5050 - Work
+61 (405) 776 431 - Mobile