From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add extra 'info os' information types for Linux (trunk and 7.4)
Date: Wed, 28 Dec 2011 06:02:00 -0000 [thread overview]
Message-ID: <834nwlwdek.fsf@gnu.org> (raw)
In-Reply-To: <4EFA54FF.1080307@earthlink.net>
> Date: Tue, 27 Dec 2011 15:30:07 -0800
> From: Stan Shebs <stanshebs@earthlink.net>
> CC: gdb-patches@sourceware.org
>
> I think the answer is that there would be few if any "info os"
> subcommands that would be genuinely common to all operating systems that
> GDB supports; embedded OSes may not even have a well-defined concept of
> processes. On the other hand, one could argue that anything that is not
> totally general should be given a OS-specific subcommand, a la "info dos".
But "info dos" is not more OS-specific than the commands suggested
here.
> And although the patch at hand consists of implementations for Linux, I
> don't think any of the types of data are truly Linux-only; the IPC types
> are common to all System V inheritors for instance, and even the
> seemingly-Linux concept of loadable kernel modules now has a BSD
> equivalent. By comparison, "info dos" has subcommands like "gdt"
> (global descriptor table) that are not meaningful for any other kind of OS.
Any modern system that runs on x86 will have a GDT, it's just that
most don't let you access it easily. So I really don't see a
fundamental difference here.
next prev parent reply other threads:[~2011-12-28 4:04 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
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 [this message]
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=834nwlwdek.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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