On Tue, Aug 14, 2012 at 10:35:39PM +0200, Hardy Griech wrote: > Hey, that came just in time! > > One "funny" remark from my side: mspdebug would have been compilable out > of the box under cygwin, if I'd used the "correct" compiler: gcc-4 > (4.5.3) produces invalid (?) code which makes mspdebug crash with > segmentation fault (with gdb one can see that "device" is changed by > printc_dbg() (tilib.c:622, "mspdebug tilib"). Perhaps one has to use > the correct compiler options?
That's strange. At this point, MSP430.DLL will be up and running, so could be due to problems linking a Cygwin binary with a "native" one perhaps. > With gcc-3 mspdebug is working (at least with tilib). > > One minor glitch: I guess, that at the end of device_probe_id(), all the > output should be directed to printc_dbg(). Yes, you're right. I'll fix that. Cheers, Daniel -- Daniel Beer <dlb...@gmail.com> www.dlbeer.co.nz IRC: inittab (Freenode) PGP key: 2048D/160A553B ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
