[
https://issues.apache.org/jira/browse/TRAFODION-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16315565#comment-16315565
]
ASF GitHub Bot commented on TRAFODION-2888:
-------------------------------------------
GitHub user selvaganesang opened a pull request:
https://github.com/apache/trafodion/pull/1376
[TRAFODION-2888] Streamline setjmp/longjmp concepts in Trafodion
First set of changes to streamline setjmp/longjmp.
a) Removed the setjmp in heap management within Trafodion.
b) Removed obsolete code related to No-wait operation concepts in SQL
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/selvaganesang/trafodion longjmp
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafodion/pull/1376.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1376
----
commit 6b6cbf93f9d51a3d605695d1f1c5f9a6c40e4578
Author: selvaganesang <selva.ganesan93@...>
Date: 2018-01-08T01:31:05Z
[TRAFODION-2888] Streamline setjmp/longjmp concepts in Trafodion
First set of changes to streamline setjmp/longjmp.
a) Removed the setjmp in heap management within Trafodion.
b) Removed obsolete code related to No-wait operation concepts in SQL
----
> Streamline setjmp/longjmp concepts in Trafodion
> -----------------------------------------------
>
> Key: TRAFODION-2888
> URL: https://issues.apache.org/jira/browse/TRAFODION-2888
> Project: Apache Trafodion
> Issue Type: Improvement
> Components: sql-general
> Reporter: Selvaganesan Govindarajan
> Assignee: Selvaganesan Govindarajan
> Fix For: 2.3
>
>
> I happened to come across a core dump with longjmp in executor layer that
> brought down the node. Unfortunately, the core dump wasn’t useful to figure
> out what was the root cause for the longjmp. Hence,
> a) I wonder is there a way to figure out what caused longjmp from the core?
> b) If no, why do longjmp? It might be better to let it dump naturally by
> accessing the invalid address or null pointer right at the point of failure.
> Was longjmp put in place in legacy Trafodion code base to avoid node being
> brought down when the privilege code gets into segment violation?
> If a) is not possible, I would want to remove the remnants of setjmp and
> longjmp from the code to enable us to debug the issue better.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
