From: Eli Zaretskii <eliz@gnu.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: stanshebs@earthlink.net, gdb-patches@sourceware.org
Subject: Re: [PATCH] Add extra 'info os' information types for Linux (trunk and 7.4)
Date: Tue, 27 Dec 2011 23:23:00 -0000 [thread overview]
Message-ID: <8362h1wu3y.fsf@gnu.org> (raw)
In-Reply-To: <201112272124.pBRLOdtk012930@glazunov.sibelius.xs4all.nl>
> Date: Tue, 27 Dec 2011 22:24:39 +0100 (CET)
> From: Mark Kettenis <mark.kettenis@xs4all.nl>
> CC: stanshebs@earthlink.net, gdb-patches@sourceware.org
>
> Eli, I don't think your objection makes a lot of sense.
That kind of argument is not an efficient way of making me change my
mind.
> The "info os"
> is a generic command for displaying "osdata" that's made available by
> the backend. It is for the backend to decide what information is made
> available. This diff just adds a bit more "osdata" to the Linux
> native backend and the Linux gdbserver remote backend.
Then let's lump there also the DOS- and Windows-specific "info"
commands for a good measure.
IOW, either "info os" is a hodgepodge of every OS-specific information
we provide about the process being debugged, or we have OS-specific
"info FOO" ("info dos", "info w32", "info linux", etc.) commands.
Having some of this and some of that is just inconsistent.
next prev parent reply other threads:[~2011-12-27 22:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 18:29 [PATCH] Add extra 'info os' information types for Linux Kwok Cheung Yeung
2011-10-21 23:38 ` Tom Tromey
2011-11-23 18:00 ` Kwok Cheung Yeung
2011-12-27 4:56 ` [PATCH] Add extra 'info os' information types for Linux (trunk and 7.4) Stan Shebs
2011-12-27 9:32 ` Eli Zaretskii
2011-12-27 21:30 ` Mark Kettenis
2011-12-27 23:23 ` Eli Zaretskii [this message]
2011-12-28 20:48 ` Mark Kettenis
2011-12-28 0:05 ` Stan Shebs
2011-12-28 3:51 ` Joel Brobecker
2011-12-28 6:02 ` Eli Zaretskii
2012-01-02 12:08 ` Pedro Alves
2012-01-02 12:35 ` Eli Zaretskii
2012-01-02 19:31 ` Pedro Alves
2012-01-03 3:05 ` Joel Brobecker
2012-01-02 18:15 ` Doug Evans
2012-01-02 19:19 ` Pedro Alves
2012-01-02 19:41 ` Tom Tromey
2011-12-29 20:34 ` Doug Evans
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=8362h1wu3y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--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