Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: gdb@sourceware.org
Subject: Need some help with xtensa processor
Date: Wed, 17 Aug 2016 00:02:00 -0000	[thread overview]
Message-ID: <268c3c75-f5b8-4eac-3999-bbf29d0ec10d@candelatech.com> (raw)

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.

So, I wanted to tell the processor to set a watchpoint on this address, and
then assert or otherwise give me an ability to grab the program counter, stack,
etc, when something writes on the memory.

I think I know how to set the BREAKA, BREAKC registers, but I must be missing something
related perhaps to setting up a proper exception vector handler for this?  Whatever
the cause, I can scribble on memory after setting the watchpoint and nothing useful
happens.

So, I'd appreciate pointers if someone has some ideas.  And, if someone wants to
work on this for pay, please contact me off-list.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


             reply	other threads:[~2016-08-17  0:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-17  0:02 Ben Greear [this message]
2016-08-17  0:11 ` Sterling Augustine
2016-08-17  0:22   ` Ben Greear
2016-09-01  4:23 doark
2016-09-01 14:18 ` 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=268c3c75-f5b8-4eac-3999-bbf29d0ec10d@candelatech.com \
    --to=greearb@candelatech.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