From: Charlls Q. <cha...@ya...> - 2011-07-04 16:57:00
|
Kapil, thanks for your reply --- El dom 19-jun-11, Kapil Arya <ka...@cc...> escribió: >> my only remaining concern is regarding statically linked applications, as shown in this page: http://dmtcp.sourceforge.net/supportedApps.html >> does this means that even having a single statically linked library will compromise the integrity of the checkpointing? what sort of caveats are there to expect when using statically linked libraries? > >DMTCP uses LD_PRELOAD facility to put wrapper around some glibc >functions so that any call from user application to any of those >functions is trapped inside DMTCP. This is no longer true in case of >static applications :(. We think it's possible to extend DMTCP to >support static applications, but due to limited resources, this is not >on our current roadmap. Sorry! > >To get an idea of what libc calls are wrapped by DMTCP, take a look at: >http://dmtcp.svn.sourceforge.net/viewvc/dmtcp/trunk/dmtcp/src/syscallwrappers.h?revision=1144&view=markup just to understand the impact of this, suppose i use certain set of dynamically link/shared libraries, but some of those libraries were build with static linkage to some of their own dependencies. Does this means potential trouble? or it only matters for the direct dependencies of the binary? |