Charm++ parallel programming system

[Gengbin Zheng <gzheng AT illinois.edu>]

Good to hear that. Looks like our fighting against the stack smashing
protection continues. But I am a little surprised that syscall
swapcontext can fail too with the same error.
We should then include this flag in the current version. Or figure out
a way to check/test longjmp error or at configure time to decide such
a flag is needed or not.
Our nightly build on local machines are on gcc 4.4.3, and so 4.5 and
later and not officially tested.
We should keep some of our machines in lab updated to the latest
version of OS and compilers for testing purpose.

Gengbin

On Sat, Mar 31, 2012 at 8:47 AM, Thomas Albers 
<talbers AT binghamton.edu>
 wrote:
> Hello!
>
> Thanks for your emails, Gengbin and Phil.
>
>>> Can you try at link time, add:
>>>   -thread context
>>> and see if it makes difference.
>>
>> Another possible fix, based on the failure you saw, is to build
>> Charm++ with -D_FORTIFY_SOURCE=0, like so:
>
> The second suggestion, building with  -D_FORTIFY_SOURCE=0, fixes the
> bug.  Building with -thread context does not make a difference,
> megatest gives the same error message as before.
>
> Do let me know if more information is needed.
>
> Regards,
> Thomas