Bill Richardson 4c3b4ea3d8 Workaround for failing tests when DEBUG=1 ...

Two changes here.

First are some failing assertions in tlcl.c. These have always failed, but
only when DEBUG=1, so no one noticed. I've opened a bug to find out why, but
it's blocking something else. We're refactoring anyway, so for now we'll
just comment around it.

Second is a null-pointer dereference in VbSharedDataSetKernelKey(). Again,
only when DEBUG=1.

BUG=chromium:379255
BRANCH=ToT
TEST=manual

  cd src/platform/ec
  \rm -rf build
  DEBUG=1 make runtests

Change-Id: Ia5e0a742f75057b449f3c19b778c5d2f0408d7cd
Signed-off-by: Bill Richardson <wfrichar@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/202303
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Reviewed-by: Luigi Semenzato <semenzato@chromium.org>

2014-05-31 01:47:51 +00:00

..

include

Get rid of some crufty macros.

2013-03-19 16:55:44 -07:00

mocked_tlcl.c

tpmc: Fix compilation with MOCK_TPM=1

2013-05-06 17:48:26 -07:00

tlcl.c

Workaround for failing tests when DEBUG=1

2014-05-31 01:47:51 +00:00