When mapping two resources in a d2d pipeline I would like to store explanatory data in the relation

[pombredanne]

When mapping two resources in a d2d pipeline I would like to store explanatory data in the relation.

For instance when I map a debug-built binary ELF to source files using DWARF debug symbols I would like to store in the relation the fact this is was mapped using one or more DWARF debug symbols of this type and with this value.

With this information, I can review and validate the results more efficiently without having to do extra research and this would provide effective tracing to explain why this mapping exists.

[tdruez]

@pombredanne Could you provide examples of the data you'd like to store to define the proper model fields?

[pombredanne]

Say that using a d2d pipeline I map the To/ binary glibc.so to the From/ glibc-2.18/libc/core/softmath.c. It could be mapped thanks to:

• a single DWARF debug symbol pointing to a compilation unit at /home/joe/toolchain/x86/glibc/2.18/libc/core/softmath.c
• one or more literals, strings or symbols extracted from the glibc.so binary and mapped to the same symbols in glibc-2.18/libc/core/softmath.c

Or in the case of Java a .class file could be mapped to a .java file thanks to:

• a combo of a java package name and a class name (a fully qualified class name)
• one or more literals, strings or symbols extracted from the foo.class binary and mapped to the same symbols in src/bar/baz/foo.kt

And going further, the binary could be mapped to source based on other attributes such as a unique copyright and license.