Trying bloaty on my IAR-compiled embedded executable yields this result.
From the -vvv output it seems that the issue occurs when bloaty is trying to deal with a section that is placed at the "RAM" addresses.
I cannot provide a sample file (sadly), but am willing to help in investigating the issue (such as running arbitrary toolchain commands on the file and extracting information from that).