[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
AW: [cdt-dev] Evaluating the output of gdb monitor commands
|
Hi Mikhail,
> Ok, now I see, though I am not sure that writing the monitor output to the
> program console is a right thing. But that's a question more to the gdb
> folks.
yeah, it is obviously the way it should be done according to the gdb manual, and I don't see any other way to do it either (i.e. no other response packet in the serial protocol that could be used).
> I checked the code and I can't see any negative consequences of collecting
> this type of data.
Well, I guess that _any_ output from the application gets sent in 'O' packets so for other commands things might be collected that are not even related to the command in progress. Though I am not sure about this. gdb might make sure that unrelated output is not mixed with running commands. No idea about that.
> Can you post the output of "monitor" in mi format including token?
Here it is:
=======snip==================
[1,133,772,933,238] (gdb)
[1,133,772,936,751] 61 monitor mbox
[1,133,772,936,753] &"monitor mbox\n"
[1,133,772,936,787] @"Box at 0x320dd56c: 0 messages\n"
[1,133,772,936,798] @"Total 1 boxes\n"
[1,133,772,936,802] 61^done
[1,133,772,936,803] (gdb)
=======snap==================
Several "Box at ..." lines for more mailboxes. My current example has only one.
I invented the format myself, of course, so I can make any modifications which would be helpful.
What are you planning to do? Will you fix the code (minor fix, just add a line or two in org.eclipse.cdt.debug.mi.core.RxThread.processMIOutput(String buffer)). Or shall I go through the enhancement-request-post-patches routine?
Thanks,
Norbert Ploett
-----Ursprüngliche Nachricht-----
Von: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Mikhail Khodjaiants
Gesendet: Donnerstag, 1. Dezember 2005 23:24
An: CDT General developers list.
Betreff: Re: [cdt-dev] Evaluating the output of gdb monitor commands
Norbert,
Ok, now I see, though I am not sure that writing the monitor output to the
program console is a right thing. But that's a question more to the gdb
folks.
I checked the code and I can't see any negative consequences of collecting
this type of data.
Can you post the output of "monitor" in mi format including token?
Thanks,
Mikhail