This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: MI -thread-list-ids output issue


On Thu, Feb 16, 2006 at 06:48:01PM +0300, Vladimir Prus wrote:
> 
> Hello!
> 
> At the moment, the response to -thread-list-ids looks like this:
> 
>   ^done,thread-ids={thread-id="3",thread-id="2",thread-id="1"},
> 
> 
> The grammar says that {} is a tuple, but not that all fields in the tuple
> have the same name, so it can be only indexed by integer. While this is
> allowed by the grammar, it's pretty inconvenient.
> 
> Essentially this will require me to add, in MI parser I use, special
> operation "treat this as list, even though it looks like a tuple", which is
> pretty nasty.
> 
> Maybe, it's still possible to change this output to be:
> 
>   ^done,thread-ids=["3","2","1"]
> 
> Or, if changing the existing output is deemed impossible even in this case,
> what about:
> 
>   ^done,threads=["3", "2", "1"],
>         thread-ids={thread-id="3",thread-id="2",thread-id="1"},

Do you have a small C example I can use to generate this output with
GDB? I would like to use the parser i have written to see if I have the
same problem you have.

Also, you wouldn't be able to change the output of MI in a non-backwards
compatible way unless a new major version of MI is released. Also, even
then, it's probably a bad idea.

Bob Rossi


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]