From: doark@mail.com
To: gdb@sourceware.org
Cc: Ben Greear <greearb@candelatech.com>
Subject: Re: Need some help with xtensa processor
Date: Thu, 01 Sep 2016 04:23:00 -0000 [thread overview]
Message-ID: <20160901002054.0e892f75@ulgy_thing> (raw)
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).
Sincerely,
David
next reply other threads:[~2016-09-01 4:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 4:23 doark [this message]
2016-09-01 14:18 ` Ben Greear
-- 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=20160901002054.0e892f75@ulgy_thing \
--to=doark@mail.com \
--cc=gdb@sourceware.org \
--cc=greearb@candelatech.com \
/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