Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"IndexError: list index out of range" while loading executable from GDB to FRDM-K64F #134

Closed
autopulated opened this issue May 12, 2015 · 4 comments
Labels

Comments

@autopulated
Copy link
Contributor

I can't reproduce this, but thought it might be useful to report anyway:

  File "/usr/local/Cellar/python/2.7.9/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 810, in __bootstrap_inner
    self.run()
  File "/usr/local/lib/python2.7/site-packages/pyOCD/gdbserver/gdbserver.py", line 153, in run
    [resp, ack, detach] = self.handleMsg(data)
  File "/usr/local/lib/python2.7/site-packages/pyOCD/gdbserver/gdbserver.py", line 220, in handleMsg
    return self.flashOp(msg[2:]), 1, 0
  File "/usr/local/lib/python2.7/site-packages/pyOCD/gdbserver/gdbserver.py", line 369, in flashOp
    self.flashData += self.unescape(data[idx_begin:len(data) - 3])
  File "/usr/local/lib/python2.7/site-packages/pyOCD/gdbserver/gdbserver.py", line 437, in unescape
    data[data_idx] = data[data_idx] ^ 0x20
IndexError: list index out of range

Version: pyOCD 0.3.2

@c1728p9
Copy link
Collaborator

c1728p9 commented May 13, 2015

Thanks for the report. Judging by the location of the crash, it looks like a gdb flashwrite packet got corrupted, causing the data to end with the escape character, 0x7d. How often do you see this? Also is your socket connection from GDB client to host on the same PC, or is it connected via the internet?

@autopulated
Copy link
Contributor Author

I've only seen this once. I'm connecting to localhost.

@autopulated
Copy link
Contributor Author

This same error just happened to me again (still on localhost). Restarting pyOCD and re-loading the same program worked fine.

@c1728p9
Copy link
Collaborator

c1728p9 commented Feb 11, 2017

Closing due to lack of activity. Please re-open if you see this again.

@c1728p9 c1728p9 closed this as completed Feb 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants