[email protected] wrote:
Control-C is currently broken in TOT lldb. It pops the input reader for the
program you are debugging off the stack, but doesn't interrupt it, leaving you
in a kind of odd state...
Greg's on this.
Jim
Thanks for this, Jim.
However, this leaves me a bit puzzled. Surely, if lldb *already* has a command intended to SIGTRAP the inferior (i.e. process interrupt), then why is Control-C broken? What is Control-C's intended
purpose in lldb?
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.
_______________________________________________
lldb-dev mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
