Re: [cdt-debug-dev] (gdb) prompt usage

[Pawel Piech <pawel.piech@xxxxxxxxxxxxx>]

Thanks Daniel,
I think this answers my question well enough :-).  Given what you said, I will assume that the secondary prompt handling in CDT is a left over communicating over pure CLI, and I'm not going to worry about it.
Thanks!
-Pawel

Daniel Jacobowitz wrote:

On Fri, Dec 01, 2006 at 09:41:34AM -0800, Pawel Piech wrote:
  

Hi,
I'm trying to descipher what is the purpose of the GDB primary and 
secondary prompts. 
It appears to me that secondary prompt is used when the CLI entered from 
the console is incomplete, and the client is expected to complete the 
command and send it. (SessionProcess.java:90) But what I find really 
confusing is that the TxThread does not pay attention to the prompt at 
all.  So whether there's a primary prompt, secondary prompt or no 
prompt, the MI commands will be sent to GDB regardless.
    

I don't know a lot about CDT, so this may not be at all the answer you
need, but anyway: don't confuse GDB's two prompts.  The default CLI
prompt is "(gdb) ", and is affected by "set prompt".  The MI prompt is
"(gdb)\n", and is not affected by anything; it's part of the protocol.