This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC] New info command for win32 native target

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.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]