Triple string from gdb-remote is hex-encoded again

Hi Greg/Jason,

This change, r218001, reverses a change I made: r214480.

I made the change (send triple as plain text), motivated by a discussion
with Jason Molenda, which started here:

http://lists.cs.uiuc.edu/pipermail/lldb-commits/Week-of-Mon-20140721/011978.html

What's happening here?

thanks
Matt

Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
More information can be found at www.csr.com. Keep up to date with CSR on our technical blog, www.csr.com/blog, CSR people blog, www.csr.com/people, YouTube, www.youtube.com/user/CSRplc, Facebook, www.facebook.com/pages/CSR/191038434253534, or follow us on Twitter at www.twitter.com/CSR_plc.
New for 2014, you can now access the wide range of products powered by aptX at www.aptx.com.

We had some places that were still hex encoding, and others that were not last week when I was getting the lldb-platform stuff working again. I didn't remember your change to plain text. Feel free to change all of the locations that set "triple" to use plain text as long as you get all of them so they are all on the same page.

Greg Clayton

Hi Greg,

That's fine. I'll just change my gdbserver back to hex-encode. As I
recollect, I only made my change after being motivated to do so after a
documentation tweak.

Matt