Hi Nausca, Apparently, DMTCP libraries are always part of the process memory map. That was true for MTCP/DMTCP-1.1.8 as well. Is there a particular case that requires those files to be not present in memory?
Best, Kapil On Mon, Oct 5, 2015 at 7:41 AM, Nausca Hsu <[email protected]> wrote: > Hi, > I recently download the 2.4.1 version to trace the source code, > And I found the latest version is some kind of hack in _ini > And _fini in the libmtcp.so before execvp a process’s main function. > > My question is, > The source code use a pthread_create in dmtcpworker’s constructor, > After the execvp, why the libmtcp.so is still at the memory, > And did not get wiped out? > > I use dmtcp_launch cat /proc/self/maps > And I can see the cat process still contains libmtcp.so in its memory > space. > > I check the publication list. > Did not found any hint. > > I am a 1.1.8 old user. > Anybody can help me to understand the latest source code? > > Thanks. > Nausca. > > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Dmtcp-forum mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dmtcp-forum > >
------------------------------------------------------------------------------
_______________________________________________ Dmtcp-forum mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dmtcp-forum
