From: Michael Chastain <mec.gnu@mindspring.com>
To: gdb-patches@sources.redhat.com, eliz@gnu.org
Subject: [rfa/doco] PROBLEMS: remove pr gdb/1505
Date: Sat, 07 Aug 2004 04:51:00 -0000 [thread overview]
Message-ID: <41145FDE.nail9GZ1WMY09@mindspring.com> (raw)
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 ----
next reply other threads:[~2004-08-07 4:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-07 4:51 Michael Chastain [this message]
2004-08-07 5:13 ` Daniel Jacobowitz
2004-08-07 7:26 ` Michael Chastain
2004-08-07 16:24 ` Daniel Jacobowitz
2004-08-07 17:04 ` Eli Zaretskii
2004-08-07 22:44 ` Michael Chastain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41145FDE.nail9GZ1WMY09@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox