This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
[rfa/doco] PROBLEMS: remove pr gdb/1505
- From: Michael Chastain <mec dot gnu at mindspring dot com>
- To: gdb-patches at sources dot redhat dot com, eliz at gnu dot org
- Date: Sat, 07 Aug 2004 00:51:42 -0400
- Subject: [rfa/doco] PROBLEMS: remove pr gdb/1505
One of the PR's in PROBLEMS has been fixed in gdb HEAD.
This patch removes the PR from PROBLEMS.
I'm not sure what to put in the title.
Leaving it as "Known problems in GDB 6.2" is wrong.
So I changed it "Known problems in GDB HEAD".
Testing: not tested.
Okay to commit?
Michael C
2004-08-07 Michael Chastain <mec.gnu@mindspring.com>
* PROBLEMS: Update title. Remove gdb/1505.
Index: PROBLEMS
===================================================================
RCS file: /cvs/src/src/gdb/PROBLEMS,v
retrieving revision 1.37
diff -c -3 -p -r1.37 PROBLEMS
*** PROBLEMS 29 Jul 2004 22:30:31 -0000 1.37
--- PROBLEMS 7 Aug 2004 04:47:48 -0000
***************
*** 1,5 ****
! Known problems in GDB 6.2
See also: http://www.gnu.org/software/gdb/bugs/
--- 1,5 ----
! Known problems in GDB HEAD
See also: http://www.gnu.org/software/gdb/bugs/
*************** mechanism. This mechanism makes it poss
*** 120,133 ****
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 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.
-
*** Threads
threads/1650: manythreads.exp
--- 120,125 ----