From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13201 invoked by alias); 12 May 2005 13:13:27 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 12466 invoked from network); 12 May 2005 13:13:08 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 12 May 2005 13:13:08 -0000 Received: from drow by nevyn.them.org with local (Exim 4.50) id 1DWDUx-000824-Na; Thu, 12 May 2005 09:13:07 -0400 Date: Thu, 12 May 2005 13:21:00 -0000 From: Daniel Jacobowitz To: Orjan Friberg Cc: gdb-patches@sources.redhat.com Subject: Re: [gdbserver/rfa] CRIS/CRISv32 gdbserver support (part 2) Message-ID: <20050512131307.GC30555@nevyn.them.org> Mail-Followup-To: Orjan Friberg , gdb-patches@sources.redhat.com References: <41E7969F.3010009@axis.com> <20050130045359.GC25185@nevyn.them.org> <41FF9274.7030700@axis.com> <20050224204906.GC11751@nevyn.them.org> <42835324.70905@axis.com> <428354B1.4020602@axis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <428354B1.4020602@axis.com> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-05/txt/msg00277.txt.bz2 On Thu, May 12, 2005 at 03:05:53PM +0200, Orjan Friberg wrote: > Orjan Friberg wrote: > > > >Another thing: when removing cris_reinsert_addr, I got the same errors > >as described in http://sourceware.org/ml/gdb/2005-01/msg00071.html (i.e. > >"thread getmsg err: no event message for getmsg" and gdbserver getting a > >SIGSEGV). > > It seems I didn't finish that thought. The reported fix for that problem > (at http://www.linux-mips.org/archives/linux-mips/2005-02/msg00103.html) > does not seem to be applicable to this case as our cache works on physical > addresses. Ah, that bug. It could be any other problem causing incoherency between the inferior and the ptracing process; there's a number of other ways to trigger the error, too. (The segfault after the error is "expected". Gdbserver is not at all robust in the face of errors which shouldn't happen in correct operation.) -- Daniel Jacobowitz CodeSourcery, LLC