On Mon, Oct 15, 2012 at 10:16:34AM +0200, Michiel Konstapel wrote: > $ git bisect bad > 08cd326e669c49adfa3c60ecc11fe75b2405427b is the first bad commit > commit 08cd326e669c49adfa3c60ecc11fe75b2405427b > Author: Daniel Beer <dlb...@gmail.com> > Date: Fri Jul 6 08:50:44 2012 +1200 > > Fix support for MSP430F2618. > > Breakpoint count is stored as a byte, not a 16-bit word. > > :040000 040000 e2aa97b9e85faa22f83b7768190f303e98805f37 > 80466e633bda25babda3023de04658739be6e1af M drivers
Hi Michiel, Thanks for doing this, but I'm still a bit puzzled. This is a change to the FET databased, but the point where identification fails in your output occurs before the database is checked. Does anything different happen if you run the version before/after the above commit with the freshly plugged-in debugger? I'm wondering if the first session of mspdebug is sending data that's screwing up identification for later sessions. - Daniel -- Daniel Beer <dlb...@gmail.com> www.dlbeer.co.nz IRC: inittab (Freenode) PGP key: 2048D/160A553B ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
