[PATCH elfutils 1/2] [libdwfl] parse inode in /proc/pid/maps correctly

2019-01-25 Thread Yonghong Song
The inode number in /proc/pid/maps is displayed as "unsigned long" type. In one of our x64 system, we have inode number exceeding valid "long" type range, which caused the following test failure: FAIL: dwfl-bug-fd-leak FAIL: run-backtrace-dwarf.sh FAIL: vdsosyms The offending map entry:

[PATCH elfutils 2/2] [tests] parse inode in /proc/pid/maps correctly in run-backtrace-data.sh

2019-01-25 Thread Yonghong Song
The backtrace-data.c parsed the inode in /proc/pid/maps with format "%*x". This caused failure if inode is big. For example, 7f269223d000-7f269226b000 r-xp 00:50 10224326387095067468 /home/... The correct format should be "%*lu" to reflect inode "unsigned long" type. But that cau

[PATCH elfutils 0/2] fix two /proc/pid/maps inode parsing issues

2019-01-25 Thread Yonghong Song
The inode number in /proc/pid/maps has type "unsigned long". The current parsing in libdwfl/linux-proc-maps.c and tests/backtrace-data.c is not correct and it triggered the following four test failures in one x64 box. FAIL: dwfl-bug-fd-leak FAIL: run-backtrace-data.sh FAIL: run-backtrace-