Chrome OS Version: R59-9460.14.0 (veyron-minnie)

What steps will reproduce the problem?
(1) Download test image and "debug-veyron-minnie.tgz" from build server.

(2) Untar somewhere accessible to chroot

(3) In chroot:

START=$(($(cgpt show chromiumos_test_image.bin  | grep ROOT-A | awk '{print $1};') * 512)) 
mkdir r 
sudo mount -oro -oloop,offset=${START} chromiumos_test_image.bin r 

(4) In chroot:

armv7a-cros-linux-gnueabi-gdb \
 -ex "set sysroot r" \
 -ex "set debug-file-directory debug/" \
 -ex "file r/opt/google/chrome/chrome"

What is the expected result? Should get dwarf info

What happens instead? Warnings like this one:

warning: Could not find DWO CU obj/third_party/WebKit/Source/modules/modules/V8EXTsRGB.dwo(0x1a8bb29b7e6ab65e) referenced by CU at offset 0xfcd60 [in module /mnt/host/source/tmp/minnie-9460.13.0-symbols/debug/opt/google/chrome/chrome.debug]

---

NOTE: in earlier builds there was no "dwarf" info being archived at all, so it wasn't terribly surprising that things weren't working.  ...but on newer builds I see the ".dwp" file so it seems like we're very close.