Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Marc Khouzam <marc.khouzam@ericsson.com>
To: "'Stan Shebs'" <stanshebs@earthlink.net>,
	       "'gdb-patches@sourceware.org'"
	<gdb-patches@sourceware.org>,
	       "'Pedro Alves'" <palves@redhat.com>
Subject: RE: 'info os' additions again
Date: Fri, 11 May 2012 20:25:00 -0000	[thread overview]
Message-ID: <F7CE05678329534C957159168FA70DEC579699C1DB@EUSAACMS0703.eamcs.ericsson.se> (raw)
In-Reply-To: <4FAC051C.1090208@earthlink.net>

> -----Original Message-----
> From: gdb-patches-owner@sourceware.org 
> [mailto:gdb-patches-owner@sourceware.org] On Behalf Of Stan Shebs
> Sent: Thursday, May 10, 2012 2:13 PM
> To: gdb-patches@sourceware.org
> Subject: Re: 'info os' additions again
> 
> On 5/10/12 5:21 AM, Pedro Alves wrote:
> > On 05/10/2012 06:18 AM, Eli Zaretskii wrote:
> >
> >>> Date: Wed, 09 May 2012 14:16:46 -0700
> >>> From: Stan Shebs<stanshebs@earthlink.net>
> >>> CC: gdb-patches@sourceware.org
> >>>
> >>>> FWIW, I never understood the reason why others prefer "info os".
> >>> I'm sure a lot of it comes from the 
> same-but-differentness of the Unix
> >>> family.  I myself have my right hand on a Macbook and 
> left hand on a
> >>> Dell running Linux, and so if I'm sticking to Posix API, 
> I want GDB to
> >>> work the same on the two.
> >> Can you show the "same but different" sub-commands we have now?
> >>
> >> What I see in osdata.c is that the info comes from a 
> target-specific
> >> XML file, so it could be anything.
> >
> > [...]
> >
> > It is more useful to consider its MI variant (has it been 
> contributed yet?  I thought
> > it had, but I can't see it now), where the frontend queries 
> GDB for what tables does
> > the backend expose (with the MI version of a plain "info 
> os", which returns
> > a table with the list of supported objects), and then 
> presents them in
> > spreadsheet-like format, all without any target-knowledge 
> hard coding.

This is exactly what we're hoping for in Eclipse. So:
- ask GDB what tables are available (-info-os without args, I gather)
- use that result to list the choice to the user
- when the user selects a table, Eclipse asks GDB for the data,
and displays it pretty much verbatim.

As Pedro points out, this would be future-proof, and any new
table could be added without changing Eclipse.

Furthermore, to fit well with Eclipse, which has very little OS-specific
code, GDB would report the list of available tables based on the OS
of the target; Eclipse would not need to consider what that OS is.
So, maybe on Windows Eclipse gets a empty table list, or very few tables,
while on Linux it gets many more.  Either way, Eclipse blindly displays
what GDB says is available.

At least that is what we were hoping for.  I hope that is possible.

Thanks for the efforts!

Marc


> > Exposing
> > more GNU/Linux objects through the mechanism in the 
> GNU/Linux backends serves
> > the purpose of being the reference implementation / 
> proof-of-concept.  Vladimir worked
> > on an Eclipse plugin that made use of all this, and it was 
> in the progress
> > of being pushed to Eclipse upstream last I heard of it.  
> I'm not aware of its
> > current status.
> 
> They're waiting for the GDB bits (including the MI patch 
> which is in my 
> queue) to become available, which is why I want to get this 
> resolved one 
> way or another.  It's a little ironic that Eclipse folks, who 
> don't care 
> about command-line syntax, are being blocked on a discussion of 
> command-line syntax. :-)
> 
> If everybody is tired of the issue, I'll just make a decision; things 
> can always be changed later.
> 
> Stan
> 
> 


      parent reply	other threads:[~2012-05-11 20:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08 22:49 Stan Shebs
2012-05-08 23:55 ` Joel Brobecker
2012-05-09  4:46 ` Eli Zaretskii
2012-05-09 21:17   ` Stan Shebs
2012-05-10  5:21     ` Eli Zaretskii
2012-05-10 12:22       ` Pedro Alves
2012-05-10 18:13         ` Stan Shebs
2012-05-10 18:18           ` Pedro Alves
2012-05-10 18:42             ` Stan Shebs
2012-05-10 18:59               ` Pedro Alves
2012-05-10 21:07                 ` Stan Shebs
2012-05-11 18:30                   ` Pedro Alves
2012-05-12  1:33                     ` Matt Rice
2012-05-14 14:52                       ` Joel Brobecker
2012-05-11 20:25           ` Marc Khouzam [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F7CE05678329534C957159168FA70DEC579699C1DB@EUSAACMS0703.eamcs.ericsson.se \
    --to=marc.khouzam@ericsson.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=stanshebs@earthlink.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox