https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #12 from Lev Veyde <lveyde at gmail dot com> --- (In reply to Nick Clifton from comment #11) > (In reply to Lev Veyde from comment #0) > Hi Lev, > > > It seems that after a few thousands of results (normally over 3000-4000) the > > addr2line in pipe mode (with -fie option) begins to randomly return > > incorrect results. > > How exactly is addr2line being run ? Can you provide an example command > line ? > > > Most frequently it begins to return file names for addresses of symbols > > which have not been defined in source files, that is instead of the expected > > ??:? > > Have you tried compiling addr2line with address sanitization enabled ? Or > running it under valgrind ? Given the description of the problem it sounds > like some kind of memory problem/buffer overrun issue. > > Cheers > Nick It's being started as: addr2line -fie vmlinux and then requests are being made to it in a loop. In our particular use case we have a code programmed in Golang that does all these requests, using this module: https://github.com/elazarl/addr2line I haven't tried compiling the addr2line in any non-default configuration, nor running it under valgrind. -- You are receiving this mail because: You are on the CC list for the bug.
