Without a symbol file I don't think there is an automated way to do it.
If your know ARM assembler, have the source code, and have a LOT of time on your hands you could probably puzzle through a disassembly of your program and figure out what source code that byte offset corresponds to. I used to do that kind of analysis, but haven't gotten that deep into it in quite a few years. (Plus I've never learned ARM assembler)
The problem is made much harder by code optimization. By default the release build setting turns on a high level of code optimization. The compiler reorders code, intermingles source statements together, unrolls loops, moves variables into registers or simplifies them away, and does lots of other tricks that make figuring out what you are looking at pretty tricky.