From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 96689 invoked by alias); 1 Sep 2016 14:18:38 -0000 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 Received: (qmail 96585 invoked by uid 89); 1 Sep 2016 14:18:37 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.7 required=5.0 tests=BAYES_50,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=narrowed, H*Ad:D*mail.com, D*candelatech.com, U*greearb X-HELO: mail2.candelatech.com Received: from mail2.candelatech.com (HELO mail2.candelatech.com) (208.74.158.173) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 01 Sep 2016 14:18:27 +0000 Received: from [50.34.199.106] (unknown [50.34.199.106]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail2.candelatech.com (Postfix) with ESMTPSA id AF45F40B24A; Thu, 1 Sep 2016 07:18:25 -0700 (PDT) Message-ID: <57C838B1.3020704@candelatech.com> Date: Thu, 01 Sep 2016 14:18:00 -0000 From: Ben Greear User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: doark@mail.com, gdb@sourceware.org Subject: Re: Need some help with xtensa processor References: <20160901002054.0e892f75@ulgy_thing> In-Reply-To: <20160901002054.0e892f75@ulgy_thing> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-09/txt/msg00002.txt.bz2 On 08/31/2016 09:20 PM, doark@mail.com wrote: > On 08/16/16(Tue) 20:01 wrote: >> Hello! >> >> I'm working on a closed source (not my decision) project that uses >> an xtensa cpu. I have no jtag access to this board, but I can pass >> messages, including grabbing 'logs' and stack traces on crash, and so >> forth. >> >> Currently, I have narrowed down a bug to a wild write on a structure of >> method pointers. Next time code tries to execute one of these methods, >> it crashes spectacularly. > > It's been about a two weeks, did you ever solve the issue? > It might be helpful to others with similar problems (you don't need to > provide identifying information). I could never get it working. My problem is likely that I do not know how to write the assembly that creates and assigns the exception vector. In the end, it was easier to track down the problem by adding asserts and debug statements... Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com