This is the mail archive of the gdb-patches@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] |
Ok I'll do that.I think it's best to keep the patches separate unless the code changes overlap.
This output is a side effect of the frame printing, the actual -thread-select command has the same. I'm going to have a look at how we can avoid it, but I think it will impact *-thread-select* as well.
I would put number-of-threads="6",current-thread-id="1" at the start so that they don't get lost behind the thread list (I know the output is only intended for the front end but it might make debugging of GDB easier and costs nothing).
Lists use square brackets, information on each thread should be enclosed in curly brackets:
threads=[{thread-id="6",frame={...},thread-extra-info="bla"},{thread-id="5",frame={...},thread-extra-info="bla"},...]
I guess your output has been manually generated as thread-id="1" seems to duplicate some information.
Yes it is, but I want to get rid of CLI commands and for front ends that want to get all informations, they could use this command if they need extra information. But I can add an option to include or not these information.
I thought that the frame information was expensive to get and that it was agreed you could get it, if needed, using other MI commands anyway.
Thanks a lot for your feedback Nick, -- Denis Pilat
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |