> Seems to be introducing a bit of regression... Some unchanged files remain ?
This assert was intended to catch the missing places that need
the fix.
Could you provide the stack backtrace from GDB and we should
know immediately what pattern to look for in the code. There
are probably a handful o
On Wed, Dec 21, 2011 at 3:54 PM, Øyvind Harboe wrote:
> Please run this in gdb and do a bt(backtrace).
Seems to be working fine, at least OpenOCD does not break.
I have in the end of the listing
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
but I guess not related to
> Commenting out this assert everything seems to be OK.
This will eventually cause a crash and must be fixed.
The fix is easy: just provide a storage for in_value when using callbacks or
checking against value/mask.
--
Øyvind Harboe - Can Zylin Consulting help on your project?
US toll free 1-86
Please run this in gdb and do a bt(backtrace).
On Wed, Dec 21, 2011 at 3:52 PM, Drasko DRASKOVIC
wrote:
> Hi all,
> with new git repo clone of OpenOCD I have been hitting this assert
> during the scan chain init :
> openocd: core.c:421: jtag_add_scan_check: Assertion
> `(field->check_value == (
Hi all,
with new git repo clone of OpenOCD I have been hitting this assert
during the scan chain init :
openocd: core.c:421: jtag_add_scan_check: Assertion
`(field->check_value == ((void *)0)) || (field->in_value != ((void
*)0))' failed.
Commenting out this assert everything seems to be OK.
I am
