[patch/rfc] PROBLEMS: Stack backtraces

[patch/rfc] PROBLEMS: Stack backtraces

[Andrew Cagney]

[-- Attachment #1: Type: text/plain, Size: 138 bytes --]

Hello,

The attached updates the PROBLEMS: Stack backtraces section so that it 
is more current.

comments, it's intended for 6.1

Andrew

[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 2442 bytes --]

2004-03-26  Andrew Cagney  <cagney@redhat.com>

	* PROBLEMS (Stack backtraces): Rewrite.  Remove reference to
	arm*-*-*.

Index: PROBLEMS
===================================================================
RCS file: /cvs/src/src/gdb/PROBLEMS,v
retrieving revision 1.23.2.3
diff -u -r1.23.2.3 PROBLEMS
--- PROBLEMS	25 Mar 2004 21:20:26 -0000	1.23.2.3
+++ PROBLEMS	26 Mar 2004 17:05:53 -0000
@@ -63,27 +63,36 @@
 
 *** Stack backtraces
 
+GDB's code base is being been updated to use a new backtrace
+mechanism.  This mechanism makes possible the support of new features
+such DWARF 2 Call Frame Information (which in turn makes possible
+backtraces through optimized code).
+
+Since this code is new, it is known to still have a few problems:
+
 gdb/1505: [regression] gdb prints a bad backtrace for a thread
 
-When backtracing a thread, gdb doesn't stop until it hits garbage.
-This is sensitive to the operating system and thread library.
+When backtracing a thread, gdb does not stop when it reaches the outer
+most frame, instead continuing until it hits garbage.  This is
+sensitive to the operating system and thread library.
 
+hppa*-*-*
 mips*-*-*
-powerpc*-*-*
-sparc*-*-*
 
-GDB's SPARC, MIPS and PowerPC targets, in 6.0, have not been updated
-to use the new frame mechanism.
+The MIPS and HPPA backtrace code has only very recently been updated
+to use GDB's new frame mechanism.  At present there are still a few
+problems, in particular backtraces through signal handlers do not
+work.
+
+People encountering problems with these architectures should consult
+GDB's web pages and mailing lists (http://www.gnu.org/software/gdb/)
+to see if there are updates.
 
-People encountering problems with these targets should consult GDB's
-web pages and mailing lists (http://www.gnu.org/software/gdb/) to see
-if there is an update.
-
-arm-*-*
+powerpc*-*-*
 
-GDB's ARM target, in 6.0, has not been updated to use the new frame
-mechanism.
+PowerPC architecture support, in 6.1, does not use the new frame code.
 
-Fortunately the ARM target, in the GDB's mainline sources, has been
-updated so people encountering problems should consider downloading a
-more current GDB (http://www.gnu.org/software/gdb/current).
+Fortunately the PowerPC architecture support, in the GDB's mainline
+sources, has been updated.  People encountering problems should
+consider downloading a more current GDB
+(http://www.gnu.org/software/gdb/current/).

Re: [patch/rfc] PROBLEMS: Stack backtraces

[Eli Zaretskii]

> Date: Fri, 26 Mar 2004 12:11:50 -0500
> From: Andrew Cagney <cagney@gnu.org>
> 
> The attached updates the PROBLEMS: Stack backtraces section so that it
> is more current.
> 
> comments, it's intended for 6.1

I think these additions are very useful, so I think they should be in
v6.1.

A couple of minor gotchas:

> +GDB's code base is being been updated to use a new backtrace
> +mechanism.  This mechanism makes possible the support of new features

I think "This mechanism makes possible to support new features" is
better.

> +such DWARF 2 Call Frame Information (which in turn makes possible
      ^^^
"such as DWARF 2 Call Frame Information", I think; ``as'' is missing.

Re: [patch/rfc] PROBLEMS: Stack backtraces

[Daniel Jacobowitz]

On Fri, Mar 26, 2004 at 07:59:48PM +0200, Eli Zaretskii wrote:
> > Date: Fri, 26 Mar 2004 12:11:50 -0500
> > From: Andrew Cagney <cagney@gnu.org>
> > 
> > The attached updates the PROBLEMS: Stack backtraces section so that it
> > is more current.
> > 
> > comments, it's intended for 6.1
> 
> I think these additions are very useful, so I think they should be in
> v6.1.
> 
> A couple of minor gotchas:
> 
> > +GDB's code base is being been updated to use a new backtrace
> > +mechanism.  This mechanism makes possible the support of new features
> 
> I think "This mechanism makes possible to support new features" is
> better.

Except that's not valid English - do you mean "makes it possible to"?

Also, "is being been".

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

Re: [patch/rfc] PROBLEMS: Stack backtraces

[Daniel Jacobowitz]

On Fri, Mar 26, 2004 at 12:11:50PM -0500, Andrew Cagney wrote:
> +When backtracing a thread, gdb does not stop when it reaches the outer
> +most frame, instead continuing until it hits garbage.  This is

I believe the standard English for this is "outermost", one word.

> -GDB's ARM target, in 6.0, has not been updated to use the new frame
> -mechanism.
> +PowerPC architecture support, in 6.1, does not use the new frame code.
>  
> -Fortunately the ARM target, in the GDB's mainline sources, has been
> -updated so people encountering problems should consider downloading a
> -more current GDB (http://www.gnu.org/software/gdb/current).
> +Fortunately the PowerPC architecture support, in the GDB's mainline

I think that the comma and "the" are incorrect?

> +sources, has been updated.  People encountering problems should
> +consider downloading a more current GDB
> +(http://www.gnu.org/software/gdb/current/).


-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

Re: [patch/rfc] PROBLEMS: Stack backtraces

[Eli Zaretskii]

> Date: Fri, 26 Mar 2004 12:11:50 -0500
> From: Andrew Cagney <cagney@gnu.org>

One more typo:

> +GDB's code base is being been updated to use a new backtrace
                   ^^^^^^^^^^^^^^^^^^^^^
I believe you wanted to say "has been updated".

Re: [patch/rfc] PROBLEMS: Stack backtraces

[Eli Zaretskii]

> Date: Fri, 26 Mar 2004 13:08:14 -0500
> From: Daniel Jacobowitz <drow@false.org>
> > 
> > I think "This mechanism makes possible to support new features" is
> > better.
> 
> Except that's not valid English - do you mean "makes it possible to"?

Yes; sorry.

Re: [patch/rfc] PROBLEMS: Stack backtraces

[Andrew Cagney]

[-- Attachment #1: Type: text/plain, Size: 27 bytes --]

I checked this in.

Andrew

[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 2446 bytes --]

2004-03-28  Andrew Cagney  <cagney@redhat.com>

	* PROBLEMS (Stack backtraces): Rewrite.  Remove reference to
	arm*-*-*.

Index: PROBLEMS
===================================================================
RCS file: /cvs/src/src/gdb/PROBLEMS,v
retrieving revision 1.23.2.4
diff -u -r1.23.2.4 PROBLEMS
--- PROBLEMS	26 Mar 2004 17:02:52 -0000	1.23.2.4
+++ PROBLEMS	28 Mar 2004 19:45:28 -0000
@@ -70,27 +70,36 @@
 
 *** Stack backtraces
 
+GDB's core code base has been updated to use a new backtrace
+mechanism.  This mechanism makes it possible to support new features
+such DWARF 2 Call Frame Information (which in turn makes possible
+backtraces through optimized code).
+
+Since this code is new, it is known to still have a few problems:
+
 gdb/1505: [regression] gdb prints a bad backtrace for a thread
 
-When backtracing a thread, gdb doesn't stop until it hits garbage.
-This is sensitive to the operating system and thread library.
+When backtracing a thread, gdb does not stop when it reaches the
+outermost frame, instead continuing until it hits garbage.  This is
+sensitive to the operating system and thread library.
 
+hppa*-*-*
 mips*-*-*
-powerpc*-*-*
-sparc*-*-*
 
-GDB's SPARC, MIPS and PowerPC targets, in 6.0, have not been updated
-to use the new frame mechanism.
+The MIPS and HPPA backtrace code has only very recently been updated
+to use GDB's new frame mechanism.  At present there are still a few
+problems, in particular backtraces through signal handlers do not
+work.
+
+People encountering problems with these architectures should consult
+GDB's web pages and mailing lists (http://www.gnu.org/software/gdb/)
+to see if there are updates.
 
-People encountering problems with these targets should consult GDB's
-web pages and mailing lists (http://www.gnu.org/software/gdb/) to see
-if there is an update.
-
-arm-*-*
+powerpc*-*-*
 
-GDB's ARM target, in 6.0, has not been updated to use the new frame
-mechanism.
+PowerPC architecture support, in 6.1, does not use the new frame code.
 
-Fortunately the ARM target, in the GDB's mainline sources, has been
-updated so people encountering problems should consider downloading a
-more current GDB (http://www.gnu.org/software/gdb/current).
+Fortunately, PowerPC architecture support, in GDB's mainline sources,
+have been updated.  People encountering problems should consider
+downloading a more current snapshot of GDB
+(http://www.gnu.org/software/gdb/current/).