This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/21225] New: Which version of gdb should I use for best reliability
- From: "richard at wetafx dot co.nz" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 07 Mar 2017 05:29:36 +0000
- Subject: [Bug gdb/21225] New: Which version of gdb should I use for best reliability
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=21225
Bug ID: 21225
Summary: Which version of gdb should I use for best reliability
Product: gdb
Version: 7.12
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: richard at wetafx dot co.nz
Target Milestone: ---
It seems that gdb has not been reliable for about a decade.
I have been using various workarounds and hacks to avoid the problems.
I have to juggle which version of gdb to use to succeed for a particular
debugging task.
Fortunately, the --readnow option can help in some of those circumstances even
with the tremendous overhead. However, gdb can still get confused and
unresponsive.
So, in the end, my question is quite simple:
Which version of gdb should I use for the best chance of reliability?
As a side question, do the developers of gdb ever use gdb to debug gdb?
As additional questions, do the developers of gdb ever debug code that use C++
or DSOs? Do the developers ever look at examples that are larger than 10K?
(To answer a potential response question, yes I am getting a bit fed up. And
if I am getting fed up, there are many more that have given up on gdb being a
useful tool.)
--
You are receiving this mail because:
You are on the CC list for the bug.