DynamoRIO / DynamoRIO/dynamorio

separate frontends from DR

Open
#1,503 0 comments 0 reactions 0 assignees View on GitHub
Component-API Migrated OpSys-All Priority-Medium Type-Feature
Dominant language
C
Stars
3.2k
Forks
629
Avg merge
2d 15h
Merged PRs (30d)
31

Description

_From [mxm...@gmail.com](https://code.google.com/u/101248221827060668005/) on August 07, 2014 14:33:50_

We aspire to separate frontends from DR but there are several issues which make it not easy to implement.
Firstly we should specify target architecture and OS since we don't use configure_DynamoRIO_\* function. So we implemented the following code to do that:

function (configure_DynamoRIO_frontend target)
get_lang(${target} tgt_lang)
if (${tgt_lang} MATCHES CXX)
set(tgt_cxx ON)
else (${tgt_lang} MATCHES CXX)
set(tgt_cxx OFF)
endif (${tgt_lang} MATCHES CXX)
DynamoRIO_extra_cflags(tgt_cflags "${tgt_cflags}" ${tgt_cxx})
set_compile_flags(${target} "${tgt_cflags} -DDYNAMORIO_STANDALONE")
endfunction (configure_DynamoRIO_frontend)

We don't commit this function b/c currently no one uses it.

Secondly we can't simply use dr_\* routines in frontends without DR. We duplicated create/remove functionality in drfrontend.h to resolve our current needs. It's a short-term solution for a long-term we should implement solution from issue #1409 (xref issue #1409)

_Original issue: http://code.google.com/p/dynamorio/issues/detail?id=1503_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.