From: Pierre Muller <muller@cerbere.u-strasbg.fr>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] New info command for win32 native target
Date: Wed, 06 Feb 2002 03:58:00 -0000 [thread overview]
Message-ID: <4.2.0.58.20020206124748.022b6e68@ics.u-strasbg.fr> (raw)
In-Reply-To: <Pine.SUN.3.91.1020206131131.3481B@is>
At 12:22 06/02/2002 , Eli Zaretskii a écrit:
>On Wed, 6 Feb 2002, Pierre Muller wrote:
>
> > This patch adds a new win32 native specific command:
> > "info sel"
>
>Thanks. A couple of comments:
>
> - this command needs to be documented in gdb.texinfo, similarly to
> "info dos ldt" and friends (and in the same chapter, but in a
> different subsection);
OK.
> - since it's a Windows-specific command, I suggest to name it
> "info w32 sel" or "info windows sel" or maybe "info cygwin sel":
> something that will tell it's not available on every platform
> (actually, using ``seg'' instead of ``sel'' might probably be even
> better, since the information you show is about a segment whose
> selector is passed as an argument);
It isn't cygwin specific, so w32 or windows is probably better.
> - I think it's a good idea to make the format used to print the segment
> as similar as possible to the one used by "info dos ..." commands;
I didn't find any command that can display individual selector info
and
"(gdb) inf dos ldt" gives
"LDT is present (at 0xc0000), but unreadable by GDB."
on my win2000 box, so I can't really try to get closer to the go32 output.
Could you please send go32 specific output?
> - why do you only print CS, DS, and FS if no argument is given? why not
> all of the segment registers? I think at least SS and GS might be
> interesting
Simply because in my experience, I always saw that
ds,es and ss are equal and that gs contains zero that is a special
selector ment to create SIGSEGV if used.
>Finally, will this work on non-x86 systems running MS-Windows (assuming
>Cygwin supports such systems)? The register names are x86-specific,
>right?
There a lots of places in win32-nat code that are i386 specific
and I don't even know if cygwin can be used to compile anything else
than i386 cpus. Maybe Christopher can answer to that one.
Pierre Muller
Institut Charles Sadron
6,rue Boussingault
F 67083 STRASBOURG CEDEX (France)
mailto:muller@ics.u-strasbg.fr
Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99
next prev parent reply other threads:[~2002-02-06 11:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 2:23 Pierre Muller
2002-02-06 3:24 ` Eli Zaretskii
2002-02-06 3:58 ` Pierre Muller [this message]
2002-02-06 4:27 ` Eli Zaretskii
2002-02-06 10:00 ` Christopher Faylor
2002-02-18 6:01 ` [RFC 2nd ver] " Pierre Muller
2002-02-18 11:32 ` Eli Zaretskii
2002-02-18 19:59 ` Christopher Faylor
2002-02-19 0:57 ` Pierre Muller
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=4.2.0.58.20020206124748.022b6e68@ics.u-strasbg.fr \
--to=muller@cerbere.u-strasbg.fr \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
/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