UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.75 Safari/537.36

Steps to reproduce the problem:
Tricky problem to reproduce!
It can occur during dumping stack traces, e.g. after a failing DCHECK, which will cause the DCHECK-message to not get printed. For example, I think this may have happened here:
https://bugs.chromium.org/p/chromium/issues/detail?id=648460&can=1&q=FindSymbol&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified#
Notice the __GI_abort caused by google::FindSymbol.
Explaining what is happening in 'What went wrong?'.

What is the expected behavior?
Don't read more symbols than there is in the section.

What went wrong?
In summary, here's what happens:
 * FindSymbol reads symbols from some object file.
 * It does this at a rate of (32 or 64) symbols per read, reading until it has read all the symbols from a section.
 * It doesn't account for the fact that there may not be an even multiple of (32 or 64) symbols in the section.
 * If there are for example 65 symbols in the section, it will try to read (31 or 63) symbols past the end of the section.
 * This will either:
    - Fail a SAFE_ASSERT because the end of the file has been reached and FindSymbol expected a multiple of sizeof(ElfW(Sym)) bytes to be read.
    - Interpret garbage data as symbols, which could have other ramifications but probably passes quietly.

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 57.0.2945.0  Channel: stable
OS Version: 
Flash Version: Shockwave Flash 23.0 r0

I will submit a fix for this.