William,
Could you try out the latest development branch:
git clone --branch=2.5 https://github.com/dmtcp/dmtcp.git
This will give you the commit 00f5f74 that Rohan refers to.
Please let us know if this works for you.
Kapil,
I think the conclusion here is that it's time to release:
dmtcp-2.5.0-rc2
Could you do that when you have a chance?
Thanks,
- Gene
On Thu, May 12, 2016 at 06:46:56PM -0400, Rohan Garg wrote:
> Gene and William,
>
> I'm not sure if it's the same bug that we fixed in commit 00f5f74. If
> it is then here's the story behind it:
>
> The bug was introduced in commit: 3a53d4f, where we added some warning
> messages using a new `warning()` API in the modify-env plugin. The warning
> API was defined in a new file `warning.cpp`, but we failed to add the
> new file to our Makefile. This was later fixed in the commit: 00f5f74
> around late Feb (see: https://github.com/dmtcp/dmtcp/commit/00f5f74),
> but it didn't make it to 2.5.0-rc1, which was release earlier in Feb.
>
> Thanks,
> Rohan
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Dmtcp-forum mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dmtcp-forum
