From: Eli Zaretskii <eliz@is.elta.co.il>
To: Pierre Muller <muller@cerbere.u-strasbg.fr>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] New info command for win32 native target
Date: Wed, 06 Feb 2002 04:27:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1020206141845.3481F-100000@is> (raw)
In-Reply-To: <4.2.0.58.20020206124748.022b6e68@ics.u-strasbg.fr>
On Wed, 6 Feb 2002, Pierre Muller wrote:
> > - 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
"info dos ldt $ds" will display the entry for DS selector's segment.
It's in the manual.
> and
> "(gdb) inf dos ldt" gives
> "LDT is present (at 0xc0000), but unreadable by GDB."
> on my win2000 box
Yes, all versions of Windows NT family don't let programs access the
descriptor tables, even for reading.
> so I can't really try to get closer to the go32 output.
> Could you please send go32 specific output?
There are examples in the GDB manual which show that, and the code is in
go32-nat.c. If the manual examples are not enough, please ask for
examples of specific commands, and I will send the 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.
I don't think it's a good idea to make decisions based on what you see in
a normal Windows program. Some programmer could do unconventional things
to segment registers, perhaps in assembly or some other way, and that's
when they will need to see them.
next prev parent reply other threads:[~2002-02-06 12:27 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
2002-02-06 4:27 ` Eli Zaretskii [this message]
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=Pine.SUN.3.91.1020206141845.3481F-100000@is \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=muller@cerbere.u-strasbg.fr \
/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