Comment 4 for bug 1367435

Unfortunately symbols.map can't capture the full ABI description. Such a list of symbols misses potential subtle ABI breaks such as structure and class member changes. That's why you always need to track the headers to get the full picture.

I'm not a big fan of symbols.map but am not opposing it either, while it doesn't get too much in the way. I know symbols.map is inaccurate right now, and very hard to make accurate while we're changing things frequently. It also has the unfortunate side-effect of bloating our tests (as they can no longer link to the real DSOs the tests need a whole second copy of each library).