202246 2007-12-14 12:59 0000 Please stabilize =sys-devel/gdb-6.7.1 2008-01-13 03:26:04 0000 1 1 1 Unclassified Gentoo Linux Ebuilds unspecified All Linux RESOLVED FIXED STABLEREQ P2 enhancement --- 1 armin76@gentoo.org toolchain@gentoo.org reavertm@gmail.com armin76@gentoo.org 2007-12-14 12:59:04 0000 +30 days in the tree, no bugs, no regressions, please do. vapier says it's okay. Expect test failures, not a regression, though. nixnut@gentoo.org 2007-12-14 19:53:44 0000 ppc stable jer@gentoo.org 2007-12-14 21:03:09 0000 Stable for HPPA. cla@gentoo.org 2007-12-15 01:48:45 0000 x86 stable ssuominen@gentoo.org 2007-12-16 11:24:27 0000 amd64 stable corsair@gentoo.org 2007-12-16 17:12:31 0000 ppc64 stable vapier@gentoo.org 2007-12-29 21:07:57 0000 *** Bug 203715 has been marked as a duplicate of this bug. *** reavertm@gmail.com 2008-01-12 04:43:40 0000 (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. vapier@gentoo.org 2008-01-12 05:59:46 0000 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 reavertm@gmail.com 2008-01-13 03:26:04 0000 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