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 2nd ver] New info command for win32 native target

At 04:59 19/02/2002 , Christopher Faylor a écrit:
>[Hmm.  I never saw the original of this message]
>On Mon, Feb 18, 2002 at 09:29:31PM +0200, Eli Zaretskii wrote:
> >> Date: Mon, 18 Feb 2002 14:59:37 +0100
> >> From: Pierre Muller <>
> >> 
> >> After the remarks from Eli and Christopher, I 
> >> change my patch to try to complete their requests.
> >
> >Thanks!
> >
> >> +@node Win32 Native
> >
> >I suggest "Windows" instead of "Win32".  Some people, including some
> >that belong to The Powers That Be, don't like calling Windows ``a
> >win'', and we don't want to rewrite large portions of the manual
> >every time they look at our documentation ;-)
>Actually, I think it should be called Cygwin.  We don't call it "MS-DOS" immediately

But while the Cygwin port is compilable only with the Cygwin tools,
it can debug any win32 API executable,
compiled with Cygwin (i.e. using the cygwin dll)
or with mingw32 (which uses msvcrt.dll)
or even other compiled by commercial compilers
(but it might not be able to use the debug info created by 
those compilers). 
I remember that there are some problems with PE executable that don't have
.code and .data sections, but 
where they are called CODE and DATA.

That is the reason why I didn't like to call it Cygwin,
but you might be right that Iwe should call the
node Cygwin native and stress inside it that it can 
debug any windows PE executable.

> >>+@cindex @sc{Win32} debugging
> >
> >It's not recommended to use @sc on a string that involves both lower-
> >and upper-case letters.

Should I change this into @sc{win32} ?

> >> +@item info w32 selector
> >> +This command displays information returned by
> >> +the Win32 API GetThreadSelectorEntry function.
> >
> >The string "GetThreadSelectorEntry" is a name of a function, so it
> >should be in @code.
> >
> >> +@item new-group
> >> +This boolean value controls whether the debuggee should
> >> +start a new group or stay in the same group as the debugger.
> >> +This affects the handling of certain Win32 exceptions.
> >
> >I think this description should be expanded a bit (what exceptions?
> >affects how?).
>I think it basically gives the inferior process its own process group.
>I think that means that if gdb sees a CTRL-C, it won't be automatically
>passed to the inferior.
>FWIW, the "info dll" command is actually the same thing as "info
>shared", if you want to add that description, too.  dll-symbols loads
>symbols from a dll similarly to add-sym but without the need to specify
>a base address.
>With the above changes, I think this is fine to check in.

I committed already the win32-nat.c code and I will resubmit the docu change.

Pierre Muller
Institut Charles Sadron
6,rue Boussingault
Phone : (33)-3-88-41-40-07  Fax : (33)-3-88-41-40-99

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