When attempting to debug an application which is instrumented using mudflap (e.g. -fmudflap during compile, with -
lmudflap during link), it seg faults in a basic printf() with the following stack dump:

Thread [1] (Suspended: Signal 'SIGSEGV' received. Description: Segmentation fault.)	
	19 _band_get_aligned()  0xfe328a0c	
	18 _band_get()  0xfe328b30	
	17 __malloc_lock()  0xfe32bd20	
	16 __malloc()  0xfe32c23c	
	15 malloc()  0xfe32b5a8	
	14 backtrace_symbols() \home\builder\hudson\gcc-trunk\svn\libmudflap\mf-runtime.c:1990 0xfe388e68	
	13 __mf_backtrace() \home\builder\hudson\gcc-trunk\svn\libmudflap\mf-runtime.c:2102 0xfe38903c	
	12 __mfu_register() \home\builder\hudson\gcc-trunk\svn\libmudflap\mf-runtime.c:1074 0xfe38a0a8	
	11 __mf_register() \home\builder\hudson\gcc-trunk\svn\libmudflap\mf-runtime.c:1174 0xfe38a1e8	
	10 malloc() \home\builder\hudson\gcc-trunk\svn\libmudflap\mf-hooks1.c:126 0xfe38bacc	
	9 _Fbuf()  0xfe356c64	
	8 _Fwprep()  0xfe357404	
	7 fwrite()  0xfe354c2c	
	6 _Fprout()  0xfe356ed4	
	5 _Printf()  0xfe35a63c	
	4 vprintf()  0xfe35648c	
	3 __mfwrap_printf() \home\builder\hudson\gcc-trunk\svn\libmudflap\mf-hooks2.c:1019 0xfe392444	
	2 usage() c:\code\keystone\src\embed\ttdk\Util\devices\src\device.c:293 0x480423d8	
	1 main() c:\code\keystone\src\embed\ttdk\Util\devices\src\device.c:1015 0x4804bba8	


But when running the applicaiton directly from the console with the same environment settings, it runs just fine.

I've tried using the IDE tool for displaying the mudflap output, as well as just adding the MUDFLAP_OPTIONS environment 
variable.

Anyone else seen this?

Thanks,

Bob