This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFC] New info command for win32 native target
- From: Pierre Muller <muller at cerbere dot u-strasbg dot fr>
- To: Eli Zaretskii <eliz at is dot elta dot co dot il>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Wed, 06 Feb 2002 12:57:37 +0100
- Subject: Re: [RFC] New info command for win32 native target
- References: <4.2.0.58.20020206103131.00ad1898@ics.u-strasbg.fr>
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