https://bugs.kde.org/show_bug.cgi?id=353192
--- Comment #16 from Fredrik Tolf <[email protected]> --- (In reply to Paul Floyd from comment #15) > Valgrind has its own DWARF reader. Certainly; I didn't mean to imply that Valgrind should actually call on gdb, I just used "info line *$address" as an example of fetching the symbol for a "file offset" address. > The problem here is detecting the conditions that trigger > looking in a segment for symbols. I'm sorry if I'm missing something again (not being a Valgrind developer, I haven't needed to delve deeply into the concrete debug-info formats and whatnot), but "looking in a segment for symbols" sounds needlessly complicated from my naïve perspective. My perspective is to look at it more as "finding the symbol for a file offset". Is that perspective not valid? You mention generating symbols for Valgrind itself as well; given that Valgrind is also mapped into the guest's address space, wouldn't that work for that case just as well? > My concern is that some of the platform hard-codedness may be really > necessary. Interesting. Are we talking about embedded architectures, or something? What would be an example of a platform where you can't match a guest address to a file path and offset? Or am I misunderstanding the problem? -- You are receiving this mail because: You are watching all bug changes.
