You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Jim Brennan (JIRA)" <ji...@apache.org> on 2018/01/30 20:49:00 UTC
[jira] [Issue Comment Deleted] (YARN-7857) -fstack-check
compilation flag causes binary incompatibility for container-executor
between RHEL 6 and RHEL 7
[ https://issues.apache.org/jira/browse/YARN-7857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Brennan updated YARN-7857:
------------------------------
Comment: was deleted
(was: The SIGSEGV reported in this Jira is a result of compiling with {{-fstack-check}}. )
> -fstack-check compilation flag causes binary incompatibility for container-executor between RHEL 6 and RHEL 7
> -------------------------------------------------------------------------------------------------------------
>
> Key: YARN-7857
> URL: https://issues.apache.org/jira/browse/YARN-7857
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 3.0.0
> Reporter: Jim Brennan
> Assignee: Jim Brennan
> Priority: Major
>
> The segmentation fault in container-executor reported in [YARN-7796] appears to be due to a binary compatibility issue with the {{-fstack-check}} flag that was added in [YARN-6721]
> Based on my testing, a container-executor (without the patch from [YARN-7796]) compiled on RHEL 6 with the -fstack-check flag always hits this segmentation fault when run on RHEL 7. But if you compile without this flag, the container-executor runs on RHEL 7 with no problems. I also verified this with a simple program that just does the copy_file.
> I think we need to either remove this flag, or find a suitable alternative.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org