From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1523 invoked by alias); 6 Feb 2002 12:27:17 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 1326 invoked from network); 6 Feb 2002 12:27:04 -0000 Received: from unknown (HELO is.elta.co.il) (199.203.121.2) by sources.redhat.com with SMTP; 6 Feb 2002 12:27:04 -0000 Received: from is (is [199.203.121.2]) by is.elta.co.il (8.9.3/8.8.8) with SMTP id OAA04144; Wed, 6 Feb 2002 14:26:08 +0200 (IST) Date: Wed, 06 Feb 2002 04:27:00 -0000 From: Eli Zaretskii X-Sender: eliz@is To: Pierre Muller cc: gdb-patches@sources.redhat.com Subject: Re: [RFC] New info command for win32 native target In-Reply-To: <4.2.0.58.20020206124748.022b6e68@ics.u-strasbg.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-02/txt/msg00164.txt.bz2 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.