.debug_line info analyzed by dmprof is not accurate

28 views
Skip to first unread message

WenSheng He

unread,
Sep 28, 2014, 11:13:37 PM9/28/14
to dmp...@chromium.org

In dmprof, source path line info is got through readelf -wL command. The following is an example output by readelf:

../../third_party/skia/include/core/SkRect.h:  ---- Currently dmprof uses this file path

/SkRect.h          474           0x11f0ac0

 

SkRect.h          474           0x11f0ac0

 

SkCanvas.cpp         1940           0x11f0ad0

 

SkCanvas.cpp         1941           0x11f0ad9  --- The better one I think should be this. But here is another problem: don't have source path, just the name 

SkCanvas.cpp         1942           0x11f0afc

I check the source of readelf tool. There is no method to get the path except modify the code to change the output format. Why not use -W flag to do this?

So, to get more accurate result of the source path, need to modify both the dmprof and readelf tool.

What's your opinion?

WenSheng He

unread,
Oct 27, 2014, 4:50:20 AM10/27/14
to dmp...@chromium.org
--- The better one I think should be this. But here is another problem: don't have source path, just the name 
It seems that objdump --dwarf=decodedline has the path. Why not use this tool?

在 2014年9月29日星期一UTC+8上午11时13分37秒,WenSheng He写道:
Reply all
Reply to author
Forward
0 new messages