Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RDKB-56987: [64BIT] Fix Runtime crash with webpa #279

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

vysakhav
Copy link

webpa process is crashing in 64bit mode against
kirkstone yocto version. The crash was due to pointer corruption as function return type casting to wrong type causing 64bit address truncated to 32bit and eventually pointer corrupted and crash occurred.

Here we could see in caller area, there is implicit function errors which as treated as warning during compilation. This is causing even though functions executed properly but when caller cast it into corresponding type, its return type wrongly mapped and resulted in corruption.

This change is mainly includes include header as well use extern to resolve the problem in casting in the caller area.

webpa process is crashing in 64bit mode against
kirkstone yocto version. The crash was due to pointer
corruption as function return type casting to wrong type
causing 64bit address truncated to 32bit and eventually
pointer corrupted and crash occurred.

Here we could see in caller area, there is implicit
function errors which as treated as warning during
compilation. This is causing even though functions
executed properly but when caller cast it into corresponding
type, its return type wrongly mapped and resulted in corruption.

This change is mainly includes include header as well use extern
to resolve the problem in casting in the caller area.

Signed-off-by: Vysakh A V <[email protected]>
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


Vysakh A V seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@vysakhav vysakhav marked this pull request as draft September 25, 2024 13:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants