From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/20887] New: Show relative change of offset
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <bug-20887-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=20887
Bug ID: 20887
Summary: Show relative change of offset
Product: libabigail
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: dodji at redhat dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
This enhancement request was filed downstream at
https://bugzilla.redhat.com/show_bug.cgi?id=1382711. I am pasting the content
of that bug here:
It would be handy to see relative change of offset when a data member changes
its offset in a data structure. Right now we get for example this:
1 data member deletion:
'FT_Generic FT_LibraryRec_::generic', at offset 64 (in bits) at
ftobjs.h:816:1
11 data member changes:
'FT_Int FT_LibraryRec_::version_major' offset changed from 192 to 64 (in bits)
'FT_Int FT_LibraryRec_::version_minor' offset changed from 224 to 96 (in bits)
'FT_Int FT_LibraryRec_::version_patch' offset changed from 256 to 128 (in
bits)
'FT_UInt FT_LibraryRec_::num_modules' offset changed from 288 to 160 (in bits)
'FT_Module FT_LibraryRec_::modules[32]' offset changed from 320 to 192 (in
bits)
'FT_ListRec FT_LibraryRec_::renderers' offset changed from 2368 to 2240 (in
bits)
'FT_Renderer FT_LibraryRec_::cur_renderer' offset changed from 2496 to 2368
(in bits)
'FT_Module FT_LibraryRec_::auto_hinter' offset changed from 2560 to 2432 (in
bits)
'FT_Byte* FT_LibraryRec_::raster_pool' offset changed from 2624 to 2496 (in
bits)
'FT_ULong FT_LibraryRec_::raster_pool_size' offset changed from 2688 to 2560
(in bits)
'FT_DebugHook_Func FT_LibraryRec_::debug_hooks[4]' offset changed from 2752 to
2624 (in bits)
It would be great if I could see there something like this:
1 data member deletion:
'FT_Generic FT_LibraryRec_::generic', at offset 64 (in bits) at
ftobjs.h:816:1
11 data member changes:
'FT_Int FT_LibraryRec_::version_major' offset changed from 192 to 64 (by 128
bits)
'FT_Int FT_LibraryRec_::version_minor' offset changed from 224 to 96 (by 128
bits)
'FT_Int FT_LibraryRec_::version_patch' offset changed from 256 to 128 (by 128
bits)
'FT_UInt FT_LibraryRec_::num_modules' offset changed from 288 to 160 (by 128
bits)
'FT_Module FT_LibraryRec_::modules[32]' offset changed from 320 to 192 (by 128
bits)
'FT_ListRec FT_LibraryRec_::renderers' offset changed from 2368 to 2240 (by
128 bits)
'FT_Renderer FT_LibraryRec_::cur_renderer' offset changed from 2496 to 2368
(by 128 bits)
'FT_Module FT_LibraryRec_::auto_hinter' offset changed from 2560 to 2432 (by
128 bits)
'FT_Byte* FT_LibraryRec_::raster_pool' offset changed from 2624 to 2496 (by
128 bits)
'FT_ULong FT_LibraryRec_::raster_pool_size' offset changed from 2688 to 2560
(by 128 bits)
'FT_DebugHook_Func FT_LibraryRec_::debug_hooks[4]' offset changed from 2752 to
2624 (by 128 bits)
This would indicate to me that this changes are caused by the deletion of the
member "generic". But if there would be another change, I would see that in
change of the relative change more easily.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-11-30 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 dodji at redhat dot com [this message]
2016-01-01 0:00 ` [Bug default/20887] " dodji at redhat dot com
2016-01-01 0:00 ` dodji at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-20887-9487@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).