+30 days in the tree, no bugs, no regressions, please do. vapier says it's okay. Expect test failures, not a regression, though.
ppc stable
Stable for HPPA.
x86 stable
amd64 stable
ppc64 stable
*** Bug 203715 has been marked as a duplicate of this bug. ***
(In reply to comment #4) > amd64 stable > No it it's not. I've been using gdb-6.7.1 on my stable gentoo amd64 as well as on Debian lenny (gcc-4.2, gdb-6.7.1) and I noticed that gdb is crashing randomly during debugging session under kdevelop (3.5.0). Problem is solved when downgraded to 6.6 on gentoo or downgraded to 6.4 on Debian (from Etch branch). There is also a note about it on http://kdevelop.org: "2007-December-04 - Sixth binary snapshot of the stable KDevelop 3.5.x release series Fixes 75 bugs from KDevelop 3.5.0 and previous versions. Again it requires GDB >= 6.4 but a regression was found in GDB versions 6.7.0 and 6.7.1, avoid them. It will be fixed in version 6.7.2" I would advise to mask versions >=6.7 in portage and fallback to 6.6.
doubtful ... feel free to post links about the bugs and i can roll a 6.7.1-r2, otherwise we'll just wait for 6.7.2
It looks something related to: http://bugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=443080 thought it's about version 6.6 (version 6.4.90 is currently marked as stable in Debian) and it may not be the case here http://sourceware.org/ml/gdb/2007-12/msg00107.html looks like my issue, because it affects communication with graphic frontends (I observed my problem on both amd64 machines: my Gentoo with gcc-4.1,gdb-6.7.x and Debian testing with gcc-4.2,gdb-6.7.x - in both cases using kdevelop-3.5.0) I'll upgrade to 6.7.1 and try to provide some scenario to reproduce
