{"push_id":543120841,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"6724fb821de490b47e0bcdf9cdff18544d24096e","before":"1172879812261067a896ec762a5e19af65970a52","commits":[{"sha":"8ae0170b85d168e70810c0d17d3e560ad777e06b","author":{"email":"36fc8141caaf059b42d857c1d91711d7ac1e2db3@rocketmail.com","name":"Martin Kojtal"},"message":"Merge pull request #87 from c1728p9/master\n\nFix SWD fault when connecting to locked Kinetis","distinct":true,"url":"https://api.github.com/repos/c1728p9/pyOCD/commits/8ae0170b85d168e70810c0d17d3e560ad777e06b"},{"sha":"6724fb821de490b47e0bcdf9cdff18544d24096e","author":{"email":"60e1c47392f378f4ce5f99199349f4dd1ce738b6@gmail.com","name":"Russ"},"message":"Fix incorrect GDB step and resume behavior\n\nWhen using GDB, a typical way of moving the execution address is to set\na breakpoint with the command 'break [line]' and then jump to that\naddress with the command 'jump [line]'.  This does not work because\nthe function maybeSkipBreakpoint will cause GDB to skip the breakpoint.\nThis patch fixes that problem by removing the function\nmaybeSkipBreakpoint.\n\nGDB single stepping still works as expected and does not get stuck\nwhen trying to step over breakpoints.  This is because the GDB\nclient automatically removes the breakpoint when stepping over it\nand restores it after.\n\nWhen using Eclipse as a GDB front end this fixes the problem where\nwhere \"Move to line\" causes the device to begin executing code,\nrather than just moving the PC.","distinct":true,"url":"https://api.github.com/repos/c1728p9/pyOCD/commits/6724fb821de490b47e0bcdf9cdff18544d24096e"}]}