From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1129 invoked by alias); 1 Mar 2007 23:30:23 -0000 Received: (qmail 1114 invoked by uid 22791); 1 Mar 2007 23:30:20 -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; Thu, 01 Mar 2007 23:30:09 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id 7BBB348CC97; Thu, 1 Mar 2007 18:30:07 -0500 (EST) 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 04056-01-8; Thu, 1 Mar 2007 18:30:07 -0500 (EST) Received: from takamaka.act-europe.fr (S0106000f3d96cb6d.vc.shawcable.net [24.84.195.170]) by nile.gnat.com (Postfix) with ESMTP id 19BEC48CC4F; Thu, 1 Mar 2007 18:30:07 -0500 (EST) Received: by takamaka.act-europe.fr (Postfix, from userid 1000) id 338E0E7B38; Thu, 1 Mar 2007 15:30:16 -0800 (PST) Date: Thu, 01 Mar 2007 23:30:00 -0000 From: Joel Brobecker To: kus Kusche Klaus Cc: gdb@sourceware.org Subject: Re: GDB for VxWorks? Message-ID: <20070301233016.GB5147@adacore.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-03/txt/msg00029.txt.bz2 > In the GDB mailing list archives, I've found two postings from you > regarding GDB for Vxworks. > > I've several questions concerning that: > * Will this be committed to GDB mainstream? Any time soon? The answer unfortunately is no. It is true that we do have a version of GDB that works with Tornado 2.x and 653, but it is simply nowhere near submitable. I am not going to enumerate all the reasons for this, but although I'm still planning on submitting all the other ports we made (native win32 and ia64-hpux), this one is not in our plans at all. > * Is the patch kept current w.r.t. the latest GDB release? How much work > would be necessary to port it to GDB 6.6? Way too much work. It would most probably be less work to do the port again from scratch. It's a bit of work, but I don't think it's all that difficult. The port itself uses ELF and DWARF, so a lot of standard pieces can be reused. Support for the various chips you mentions is also already there. So all you really need to do is implement support for WTX. From our experience, the only tricky parts are: . Implement the main event loop . Get some of the information we need, such as the list of task (aka "threads"). You'll need to poke directly in the memory for that using gopher, at least with 653. There is not support for that that's provided by the system. Check "gdb.tcl" in the tornado install files, this gives a bit of insight on that. > * Does this work with VxWorks 5, VxWorks 6, or both? VxWorks 5 and 653. > * What target hardware platforms does it support (we use Pentium, PPC > and XScale)? We only support x86 and ppc. The patch we inherited supported many platforms, such as hppa, or m68k, but we are not testing on these, so I don't know. I don't think xscale is supported, however. > * How can I download it (our firewall does not allow CVS access, only > http and ftp)? At the present moment, we do not provide public access to this patch. I don't think it would be much use to you either. I recommend instead that you contact WindRiver directly; they should be able to provide you the debugger and their sources - they were the original implementors of that port. -- Joel