From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16555 invoked by alias); 13 Jun 2006 06:05:33 -0000 Received: (qmail 16547 invoked by uid 22791); 13 Jun 2006 06:05:33 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 13 Jun 2006 06:05:31 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id F148548CC3D; Tue, 13 Jun 2006 02:05:28 -0400 (EDT) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 04381-01-10; Tue, 13 Jun 2006 02:05:28 -0400 (EDT) Received: from takamaka.act-europe.fr (s142-179-108-108.bc.hsia.telus.net [142.179.108.108]) by nile.gnat.com (Postfix) with ESMTP id 75A7348CBFE; Tue, 13 Jun 2006 02:05:28 -0400 (EDT) Received: by takamaka.act-europe.fr (Postfix, from userid 507) id B2DA347E7F; Mon, 12 Jun 2006 23:05:23 -0700 (PDT) Date: Tue, 13 Jun 2006 10:12:00 -0000 From: Joel Brobecker To: Kameswari S Cc: gdb@sources.redhat.com Subject: Re: Reg-GDB version Message-ID: <20060613060523.GT17410@adacore.com> References: <448E46E2.9090505@tcs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <448E46E2.9090505@tcs.com> User-Agent: Mutt/1.4i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-06/txt/msg00075.txt.bz2 > Can you tell me the latest GDB version for Solaris 2.9 ? Could you > please tell me from where I can download it? If there are any concerned > persons can you give the mailid's for contact. The latest released version of GDB is GDB 6.4, which is available from the GDB website. This version is known to work on Solaris 2.9. I'm away all of next week, but it is my intention to release 6.5 very-soon-now, probably in a week, maybe even next week while I travel. Apparently, there is a known problem in 6.5 with thread debugging so you might want to stick to 6.4 for now. I'm hoping we can fix this problem for 6.5.1. -- Joel