* [patch/commit] News cleanups.
@ 2002-08-03 17:03 Andrew Cagney
2002-08-03 22:47 ` Daniel Jacobowitz
0 siblings, 1 reply; 6+ messages in thread
From: Andrew Cagney @ 2002-08-03 17:03 UTC (permalink / raw)
To: gdb-patches
[-- Attachment #1: Type: text/plain, Size: 79 bytes --]
Hello,
I've committed the following cleanups to the NEWS file.
enjoy,
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1752 bytes --]
2002-08-03 Andrew Cagney <ac131313@redhat.com>
* NEWS: Cleanup. Use *-linux*-gnu*. Only use `*' for headings.
Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.82
diff -u -r1.82 NEWS
--- NEWS 1 Aug 2002 17:18:32 -0000 1.82
+++ NEWS 4 Aug 2002 00:00:40 -0000
@@ -5,9 +5,9 @@
* ``gdbserver'' now supports multithreaded applications on some targets
-Support for multithreaded applications using LinuxThreads has been added
-for arm*-*-linux*, i[3456]86-*-linux*, mips*-*-linux*, powerpc*-*-linux*,
-and sh*-*-linux*.
+Support for multithreaded applications using libthread_db has been
+added for arm*-*-linux*-gnu*, i[3456]86-*-linux*-gnu*,
+mips*-*-linux*-gnu*, powerpc*-*-linux*-gnu*, and sh*-*-linux*-gnu*.
* GDB now supports C/C++ preprocessor macros.
@@ -15,21 +15,16 @@
and provides various commands for showing macro definitions and how
they expand.
+The new command `macro expand EXPRESSION' expands any macro
+invocations in expression, and shows the result.
+
+The new command `show macro MACRO-NAME' shows the definition of the
+macro named MACRO-NAME, and where it was defined.
+
Most compilers don't include information about macros in the debugging
information by default. In GCC 3.1, for example, you need to compile
your program with the options `-gdwarf-2 -g3'. If the macro
information is present in the executable, GDB will read it.
-
-Here are the new commands for working with macros:
-
-** macro expand EXPRESSION
-
-Expand any macro invocations in expression, and show the result.
-
-** show macro MACRO-NAME
-
-Show the definition of the macro named MACRO-NAME, and where it was
-defined.
* Multi-arched targets.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [patch/commit] News cleanups.
2002-08-03 17:03 [patch/commit] News cleanups Andrew Cagney
@ 2002-08-03 22:47 ` Daniel Jacobowitz
2002-08-04 7:48 ` Andrew Cagney
0 siblings, 1 reply; 6+ messages in thread
From: Daniel Jacobowitz @ 2002-08-03 22:47 UTC (permalink / raw)
To: Andrew Cagney; +Cc: gdb-patches
On Sat, Aug 03, 2002 at 08:03:52PM -0400, Andrew Cagney wrote:
> Hello,
>
> I've committed the following cleanups to the NEWS file.
>
> enjoy,
> Andrew
> 2002-08-03 Andrew Cagney <ac131313@redhat.com>
>
> * NEWS: Cleanup. Use *-linux*-gnu*. Only use `*' for headings.
>
> Index: NEWS
> ===================================================================
> RCS file: /cvs/src/src/gdb/NEWS,v
> retrieving revision 1.82
> diff -u -r1.82 NEWS
> --- NEWS 1 Aug 2002 17:18:32 -0000 1.82
> +++ NEWS 4 Aug 2002 00:00:40 -0000
> @@ -5,9 +5,9 @@
>
> * ``gdbserver'' now supports multithreaded applications on some targets
>
> -Support for multithreaded applications using LinuxThreads has been added
> -for arm*-*-linux*, i[3456]86-*-linux*, mips*-*-linux*, powerpc*-*-linux*,
> -and sh*-*-linux*.
> +Support for multithreaded applications using libthread_db has been
> +added for arm*-*-linux*-gnu*, i[3456]86-*-linux*-gnu*,
> +mips*-*-linux*-gnu*, powerpc*-*-linux*-gnu*, and sh*-*-linux*-gnu*.
>
> * GDB now supports C/C++ preprocessor macros.
>
I don't really agree with the first bit. The applications are using
LinuxThreads (capitalization uncertain), not libthread_db; the user
doesn't care what the debugger is using...
> @@ -15,21 +15,16 @@
> and provides various commands for showing macro definitions and how
> they expand.
>
> +The new command `macro expand EXPRESSION' expands any macro
> +invocations in expression, and shows the result.
> +
> +The new command `show macro MACRO-NAME' shows the definition of the
> +macro named MACRO-NAME, and where it was defined.
> +
> Most compilers don't include information about macros in the debugging
> information by default. In GCC 3.1, for example, you need to compile
> your program with the options `-gdwarf-2 -g3'. If the macro
> information is present in the executable, GDB will read it.
> -
> -Here are the new commands for working with macros:
> -
> -** macro expand EXPRESSION
> -
> -Expand any macro invocations in expression, and show the result.
> -
> -** show macro MACRO-NAME
> -
> -Show the definition of the macro named MACRO-NAME, and where it was
> -defined.
>
> * Multi-arched targets.
>
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [patch/commit] News cleanups.
2002-08-03 22:47 ` Daniel Jacobowitz
@ 2002-08-04 7:48 ` Andrew Cagney
2002-08-04 7:52 ` Daniel Jacobowitz
0 siblings, 1 reply; 6+ messages in thread
From: Andrew Cagney @ 2002-08-04 7:48 UTC (permalink / raw)
To: Daniel Jacobowitz; +Cc: gdb-patches
> -Support for multithreaded applications using LinuxThreads has been added
>> -for arm*-*-linux*, i[3456]86-*-linux*, mips*-*-linux*, powerpc*-*-linux*,
>> -and sh*-*-linux*.
>> +Support for multithreaded applications using libthread_db has been
>> +added for arm*-*-linux*-gnu*, i[3456]86-*-linux*-gnu*,
>> +mips*-*-linux*-gnu*, powerpc*-*-linux*-gnu*, and sh*-*-linux*-gnu*.
Is ``Support for debugging multi-threaded applications, that use
GNU/Linux's thread library, has been added.'' better?
enjoy,
Andrew
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [patch/commit] News cleanups.
2002-08-04 7:48 ` Andrew Cagney
@ 2002-08-04 7:52 ` Daniel Jacobowitz
2002-08-04 8:01 ` Andrew Cagney
0 siblings, 1 reply; 6+ messages in thread
From: Daniel Jacobowitz @ 2002-08-04 7:52 UTC (permalink / raw)
To: Andrew Cagney; +Cc: gdb-patches
On Sun, Aug 04, 2002 at 10:48:35AM -0400, Andrew Cagney wrote:
> >-Support for multithreaded applications using LinuxThreads has been added
> >>-for arm*-*-linux*, i[3456]86-*-linux*, mips*-*-linux*, powerpc*-*-linux*,
> >>-and sh*-*-linux*.
> >>+Support for multithreaded applications using libthread_db has been
> >>+added for arm*-*-linux*-gnu*, i[3456]86-*-linux*-gnu*,
> >>+mips*-*-linux*-gnu*, powerpc*-*-linux*-gnu*, and sh*-*-linux*-gnu*.
>
> Is ``Support for debugging multi-threaded applications, that use
> GNU/Linux's thread library, has been added.'' better?
I'd say ``Support for debugging multi-threaded applications which use
the GNU/Linux LinuxThreads package has been added.'' Because I believe
``which'' and ``that'' aren't supposed to start parentheticals, and
because LinuxThreads is not "GNU/Linux's thread library"; there are at
least two or three others.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [patch/commit] News cleanups.
2002-08-04 7:52 ` Daniel Jacobowitz
@ 2002-08-04 8:01 ` Andrew Cagney
2002-08-04 8:12 ` Daniel Jacobowitz
0 siblings, 1 reply; 6+ messages in thread
From: Andrew Cagney @ 2002-08-04 8:01 UTC (permalink / raw)
To: Daniel Jacobowitz; +Cc: gdb-patches
> On Sun, Aug 04, 2002 at 10:48:35AM -0400, Andrew Cagney wrote:
>
>> >-Support for multithreaded applications using LinuxThreads has been added
>
>> >>-for arm*-*-linux*, i[3456]86-*-linux*, mips*-*-linux*, powerpc*-*-linux*,
>> >>-and sh*-*-linux*.
>> >>+Support for multithreaded applications using libthread_db has been
>> >>+added for arm*-*-linux*-gnu*, i[3456]86-*-linux*-gnu*,
>> >>+mips*-*-linux*-gnu*, powerpc*-*-linux*-gnu*, and sh*-*-linux*-gnu*.
>
>>
>> Is ``Support for debugging multi-threaded applications, that use
>> GNU/Linux's thread library, has been added.'' better?
>
>
> I'd say ``Support for debugging multi-threaded applications which use
> the GNU/Linux LinuxThreads package has been added.'' Because I believe
> ``which'' and ``that'' aren't supposed to start parentheticals, and
> because LinuxThreads is not "GNU/Linux's thread library"; there are at
> least two or three others.
Which ever :-) You or me to commit?
Andrew
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [patch/commit] News cleanups.
2002-08-04 8:01 ` Andrew Cagney
@ 2002-08-04 8:12 ` Daniel Jacobowitz
0 siblings, 0 replies; 6+ messages in thread
From: Daniel Jacobowitz @ 2002-08-04 8:12 UTC (permalink / raw)
To: Andrew Cagney; +Cc: gdb-patches
On Sun, Aug 04, 2002 at 11:00:56AM -0400, Andrew Cagney wrote:
> >On Sun, Aug 04, 2002 at 10:48:35AM -0400, Andrew Cagney wrote:
> >
> >>>-Support for multithreaded applications using LinuxThreads has been added
> >
> >>>>-for arm*-*-linux*, i[3456]86-*-linux*, mips*-*-linux*,
> >>powerpc*-*-linux*,
> >>>>-and sh*-*-linux*.
> >>>>+Support for multithreaded applications using libthread_db has been
> >>>>+added for arm*-*-linux*-gnu*, i[3456]86-*-linux*-gnu*,
> >>>>+mips*-*-linux*-gnu*, powerpc*-*-linux*-gnu*, and sh*-*-linux*-gnu*.
> >
> >>
> >>Is ``Support for debugging multi-threaded applications, that use
> >>GNU/Linux's thread library, has been added.'' better?
> >
> >
> >I'd say ``Support for debugging multi-threaded applications which use
> >the GNU/Linux LinuxThreads package has been added.'' Because I believe
> >``which'' and ``that'' aren't supposed to start parentheticals, and
> >because LinuxThreads is not "GNU/Linux's thread library"; there are at
> >least two or three others.
>
> Which ever :-) You or me to commit?
I did it:
2002-08-04 Daniel Jacobowitz <drow@mvista.com>
* NEWS: Cleanup and nitpick.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2002-08-04 15:12 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-08-03 17:03 [patch/commit] News cleanups Andrew Cagney
2002-08-03 22:47 ` Daniel Jacobowitz
2002-08-04 7:48 ` Andrew Cagney
2002-08-04 7:52 ` Daniel Jacobowitz
2002-08-04 8:01 ` Andrew Cagney
2002-08-04 8:12 ` Daniel Jacobowitz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox