mirror/binutils-gdb
2
0
Fork 0
mirror of https://sourceware.org/git/binutils-gdb.git synced 2024-11-27 03:51:15 +08:00
Code Issues Packages Projects Releases Wiki Activity

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

Browse Source 
* PROBLEMS (Stack backtraces): Rewrite.  Remove reference to
	arm*-*-*.
This commit is contained in:
Andrew Cagney 2004-03-28 19:56:41 +00:00
parent 6a1b180db4
commit 72b5645881
2 changed files with 31 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/ChangeLog
View File

@ -1,3 +1,8 @@
2004-03-28 Andrew Cagney <cagney@redhat.com>
* PROBLEMS (Stack backtraces): Rewrite. Remove reference to
arm*-*-*.
2004-03-28 Stephane Carrez <stcarrez@nerim.fr>
* tui/tui-regs.c (tui_show_registers): Make sure the TUI is active

43
gdb/PROBLEMS
View File

@ -70,27 +70,36 @@ ABI for C++ which requires multiple object code functions.
*** 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*-*-*
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.
powerpc*-*-*
sparc*-*-*
GDB's SPARC, MIPS and PowerPC targets, in 6.0, have not been updated
to use the new frame mechanism.
PowerPC architecture support, in 6.1, does not use the new frame code.
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-*-*
GDB's ARM target, in 6.0, has not been updated to use the new frame
mechanism.
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/).