06:02 <zapb_> karlp, master?

06:03 <zapb_> karlp, never experience this issue, did you check the code?

09:22 <karlp> yeah, that's where my debug came from.

09:22 <karlp> um, close to master, yeah,

09:23 <karlp> cant' see anything recent that would matter.

09:23 <karlp> it's like the target_read_buffer is getting somethign back weird.

09:23 <karlp> I cant' see anything in the code that looks remotely sus, and "x" ingdb never shows me anythign other than what the map file says...

09:37 <karlp> reapplying my patches on top of todays master, see if it keeps happening or not..

10:29 <karlp> in "just grumbling" this is the "winning" from using the system jimtcl now: https://paste.jvnv.net/view/7YJkl :)

10:31 <Haohmaru> what are you brewing?

20:09 <dgz> Hi - this question is purely out of curiosity, but why was the last stable release of OpenOCD nearly 2 years ago at this point given all of the changes on the master branch in that time?

20:09 <dgz> (not really sure how to word that over text without sounding like a demanding asshole - that is not the intention)

20:17 <zapb_> dgz, making a release takes time ;)

20:20 <dgz> zapb_: sure... it's just a bit difficult to know if the master branch is reliable - e.g., I have an MSPM0 device which only just started to exist in OpenOCD thanks to TI. So far, it appears to be working okay at least

20:21 <zapb_> dgz, the master branch is quite stable thanks to all the reviewers

20:22 <zapb_> but hopefully there will be a release this year