From: Ben Greear <greearb@candelatech.com>
To: doark@mail.com, gdb@sourceware.org
Subject: Re: Need some help with xtensa processor
Date: Thu, 01 Sep 2016 14:18:00 -0000 [thread overview]
Message-ID: <57C838B1.3020704@candelatech.com> (raw)
In-Reply-To: <20160901002054.0e892f75@ulgy_thing>
On 08/31/2016 09:20 PM, doark@mail.com wrote:
> On 08/16/16(Tue) 20:01 <greearb@candelatech.com> 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 <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2016-09-01 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 4:23 doark
2016-09-01 14:18 ` Ben Greear [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-08-17 0:02 Ben Greear
2016-08-17 0:11 ` Sterling Augustine
2016-08-17 0:22 ` Ben Greear
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57C838B1.3020704@candelatech.com \
--to=greearb@candelatech.com \
--cc=doark@mail.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox