This is the mail archive of the 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: [PATCH] Add the "-info-os" command to MI

> Date: Thu, 13 Oct 2011 16:51:49 +0100
> From: Kwok Cheung Yeung <>
> This patch adds the "-info-os" command to MI as the counterpart to the GDB "info 
> os" command. It behaves in the same way as "info os", only the output is 
> formatted according to MI conventions. I've also added an entry in the 
> documentation.


>   On @sc{gnu}/Linux, the following values of INFOTYPE are valid:
> -@anchor{linux info os infotypes}
> +@anchor{Linux OS information types}

I don't see these lines in today's CVS version of gdb.texinfo.  Does
your patch depend on some other patch?

Anyway, why is "info os processes" suddenly treated as a
Linux-specific command?  "info os" is supposed to be
platform-agnostic; if it is a Linux-only feature, it will be more
appropriate to call it "info linux", like "info dos" and "info w32"
that we already have.

> +The types of information available depend on the target operating
> +system.  The available types for @sc{gnu}/Linux are listed in
> +@ref{Linux OS information types}.

As I said above, the referenced section is not Linux-specific, and the
CVS version of the manual does not have any details there.  So
something (perhaps in my brain) is missing.

> +@smallexample
> +(gdb)
> +-info-os
> +^done,OSDataTable=@{nr_rows="9",nr_cols="2",hdr=[@{width="10",alignment=
> +"-1",col_name="col0",colhdr="Type"@},@{width="10",alignment="-1",col_nam
> +e="col1",colhdr="Description"@}],body=[item=@{col0="processes",col1="Lis
> +ting of all processes"@},item=@{col0="procgroups",col1="Listing of all p
> +rocess groups"@},item=@{col0="threads",col1="Listing of all threads"@},i
> +tem=@{col0="files",col1="Listing of all file descriptors"@},item=@{col0=
> +"sockets",col1="Listing of all internet-domain sockets"@},item=@{col0="s
> +hm",col1="Listing of all shared-memory regions"@},item=@{col0="semaphore
> +s",col1="Listing of all semaphores"@},item=@{col0="msg",col1="Listing of
> + all message queues"@},item=@{col0="modules",col1="Listing of all loaded
> + kernel modules"@}]@}

The lines here are broken in arbitrary places, which will look
illegible in the manual.  Please reformat the example so that the
output could be readable by humans.


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