https://bugs.kde.org/show_bug.cgi?id=473974
Bug ID: 473974
Summary: aspacem output for file segments wrong with clang 14
Classification: Developer tools
Product: valgrind
Version: 3.22 GIT
Platform: Compiled Sources
OS: FreeBSD
Status: REPORTED
Severity: minor
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: pjfl...@wanadoo.fr
Target Milestone: ---
File segements get output with
VG_(debugLog)(
logLevel, "aspacem",
"%3d: %s %010lx-%010lx %s %c%c%c%c%c d=0x%03llx "
"i=%-7llu o=%-7lld (%d,%d)\n",
segNo, show_SegKind(seg->kind),
seg->start, seg->end, len_buf,
seg->hasR ? 'r' : '-', seg->hasW ? 'w' : '-',
seg->hasX ? 'x' : '-', seg->hasT ? 'T' : '-',
seg->isCH ? 'H' : '-',
seg->dev, seg->ino, seg->offset,
ML_(am_segname_get_seqnr)(seg->fnIdx), seg->fnIdx
);
The component for the device is
d=0x%03llx
which is a long with width 3 and zero padding.
clang14 produces
--PID:1: aspacem 1: file 0000108000-0000108fff 4096 r----
d=0x28a8dde4190bc5c i=1050513 o=0 (1,73)
with a width of 15 that looks wrong
whilst clang16 produces
--PID:1: aspacem 1: file 0000108000-0000108fff 4096 r---- d=0x05a i=801704
o=0 (1,61)
with a width of 3 that looks right
--
You are receiving this mail because:
You are watching all bug changes.
