From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25418 invoked by alias); 12 Oct 2009 17:56:10 -0000 Received: (qmail 25409 invoked by uid 22791); 12 Oct 2009 17:56:09 -0000 X-SWARE-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,BAYES_40 X-Spam-Check-By: sourceware.org Received: from fmmailgate04.web.de (HELO fmmailgate04.web.de) (217.72.192.242) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 12 Oct 2009 17:56:04 +0000 Received: from web.de by fmmailgate04.web.de (Postfix) with SMTP id DDDC361EBEDF; Mon, 12 Oct 2009 19:56:01 +0200 (CEST) Received: from [87.174.191.73] by freemailng1401.web.de with HTTP; Mon, 12 Oct 2009 19:56:00 +0200 Date: Mon, 12 Oct 2009 17:56:00 -0000 Message-Id: <1193752320@web.de> MIME-Version: 1.0 From: damny@web.de To: Joel Brobecker , gdb@sourceware.org Subject: Re: build a canadian cross gdb Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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: 2009-10/txt/msg00214.txt.bz2 > > You are still incorrect. Like I said before, if OpenOCD crashes, the > > bug is in OpenOCD. > > In other words, even if GDB did send something that OpenOCD did not like, > whether correct or not, OpenOCD should still not crash. ok ... your partially right, if openocd get a faulty gdb communication, openocd has to catch it. but ... logical consequences. => gdb-6.8.50.20080308-cvs build on windows works with openocd for windows => gdb-6.7.50.200080229 (older version than the working one) build on linux for windows doesn't work with openocd for windows => gdb-6.8 (the most exact equal version like the working one) build on linux for windows doesn't work with openocd for windows => gdb-6.8.50.20090801 (newer version than the working one) build on linux for windows doesn't work with openocd for windows => gdb-7.0.50.20090926 (newer version than the working one) build on linux for windows doesn't work with openocd for windows => older, nearly exact and newer versions (than the named above) of gdb build on linux for windows doesn't work with openocd for windows => openocd online docs say "Use GDB 6.7 or newer with OpenOCD if you run into trouble." => it's only a (new) assumption, but i estimate that remote protocol didn't changed so drastic in 6.8.50 versions; so i think my original used version gdb version (6.8.50.20090801) should work like gdb-6.8.50.20080308-cvs the main difference between 'working' and 'not working' is the way of the build process, respectively the build system ('windows' <=> 'linux'). my assumption from first post (tui, termcap, ncurses) was highly speculative. that's why i searched for help. so i ask again: has anybody of you experiences in building gdb the way i try it (canadian cross with build=i686-linux-gnu, host=i586-mingw32msvc, target=arm-elf)? does anybody know if there are gdb patches for canadian cross builds, ...? and some new questions: was this actually done before? is anybody here that know/use openocd and has experiences in the way of communication of openocd and gdb? thanks again, daniel _______________________________________________________________ Neu: WEB.DE DSL bis 50.000 kBit/s und 200,- Euro Startguthaben! http://produkte.web.de/go/02/