From owner-freebsd-bugs@FreeBSD.ORG Mon Oct 13 07:00:19 2008 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 266B11065688 for ; Mon, 13 Oct 2008 07:00:19 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 157318FC25 for ; Mon, 13 Oct 2008 07:00:19 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id m9D70Il6077234 for ; Mon, 13 Oct 2008 07:00:18 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id m9D70Iif077233; Mon, 13 Oct 2008 07:00:18 GMT (envelope-from gnats) Date: Mon, 13 Oct 2008 07:00:18 GMT Message-Id: <200810130700.m9D70Iif077233@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Victor Sudakov Cc: Subject: Re: gnu/124970: gdb(1): gdb crashes after setting hardware watchpoint X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Victor Sudakov List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Oct 2008 07:00:19 -0000 The following reply was made to PR gnu/124970; it has been noted by GNATS. From: Victor Sudakov To: "Dorr H. Clark" Cc: bug-followup@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: gnu/124970: gdb(1): gdb crashes after setting hardware watchpoint Date: Mon, 13 Oct 2008 12:54:07 +0700 Dorr H. Clark wrote: > > We believe that the problem reported in PR 124970 has been fixed in gdb 6.2.1. > > The latest port for gdb6 is 6.6.1 in 7.0-Release. However, 7.0 was distributed > with the 6.1.1 release of gdb. We recommend that the gdb port in the 7.x > release series be upgraded to address this issue. Note that FreeBSD 6.3 > also has the same version of gdb with the same problem. > > What follows is a detailed discussion of the issue and a patch. > > In addition to patching gdb itself, switching locally to gdb 6.6.1 is > another workaround for users concerned about this bug. Thank you for your effort, I will use gdb from the ports collection. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:sudakov@sibptus.tomsk.ru