From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23659 invoked by alias); 22 Sep 2006 20:32:47 -0000 Received: (qmail 23564 invoked by uid 22791); 22 Sep 2006 20:32:47 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 22 Sep 2006 20:32:45 +0000 Received: (qmail 27866 invoked from network); 22 Sep 2006 20:32:43 -0000 Received: from unknown (HELO localhost) (jimb@127.0.0.2) by mail.codesourcery.com with ESMTPA; 22 Sep 2006 20:32:43 -0000 To: Maxim Grigoriev Cc: gdb-patches@sources.redhat.com, Bob Wilson , chris Zankel Subject: Re: Xtensa port References: <45142A88.7000805@hq.tensilica.com> From: Jim Blandy Date: Fri, 22 Sep 2006 20:32:00 -0000 In-Reply-To: <45142A88.7000805@hq.tensilica.com> (Maxim Grigoriev's message of "Fri, 22 Sep 2006 11:25:12 -0700") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-09/txt/msg00151.txt.bz2 Maxim Grigoriev writes: > Basic Xtensa port. It doesn't include any targets. The next step will be > a submission of "xtensa*-*-linux" target. It will include gdbserver port and > everything else necessary to debug Xtensa code on this target. Thanks for the contribution! I haven't looked at the code closely, but I have a few questions. - Where does xtensa-config.h come from? - Does xtensa-config.c need to be listed in ALLDEPFILES as well? - I don't see anything that actually plugs in xtensa-linux-tdep.o. Should that be kept out until the linux target is ready? - In your DejaGnu config files, there is a way to tell GDB not to run tests that depend on the inferior being able to do I/O; this is used to run the tests against embedded systems that don't implement the semi-hosting protocol packets, like yours. Look for uses of 'gdb_skip_stdio_test'. - Can you explain more about the differences between the Xtensa-generated DWARF and what GDB expects? Ideally, GDB should accept DWARF from any compiler, but because DWARF is so flexible it's easy for inappropriate expectations to creep in.