RE: [cdt-debug-dev] preventing MI commands from appearing in the gdbcons

["Mikhail Khodjaiants" <Mikhail.Khodjaiants@xxxxxxx>]

Hi Derek,

"setQuiet" prevents the propagation of MI events to the upper layer.
You can use the "enableConsole" method in the RxThread that stops the
console output. See for example "SharedLibraryManager.getMIShared".

Regrads,
Mikhail
-----Original Message-----
From: cdt-debug-dev-bounces@xxxxxxxxxxx
[mailto:cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of Derek Morris
Sent: 10 November 2006 12:53
To: CDT Debug developers list
Subject: [cdt-debug-dev] preventing MI commands from appearing in the
gdbconsole

Hi,

I have extended the launch configuration to send some additional
commands to GDB. My code looks like this:

CLICommand cli = new CLICommand(commands[j]);
cli.setQuiet(true) ;
miSession.postCommand(cli, manyYears);
MIInfo info = cli.getMIInfo();
if (info == null) {
	throw new MIException("Timeout"); //$NON-NLS-1$ } else {
	parseOutput(miSession, info, commands[j], errors) ; }
					}
These commands appear in the GDB console window, as does their response.
Is there any way to suppress this - I'd like to hide this added
complication from the user.

It must be possible, as you don't see the stream of MI commands flowing
between Eclipse and GDB when stepping etc.

I was hoping that cli.setQuiet() would do this for me, but it doesn't.

TIA

--
Derek
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev

-- 
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.