[
https://issues.apache.org/jira/browse/KUDU-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Percy updated KUDU-2433:
-----------------------------
Description: Edit:
ClientFailoverOnNegotiationTimeoutITest.Kudu1580ConnectToTServer failed in ASAN
mode with what appeared to be a flake, but after more investigation (see
attached log file) there appears to be some case where the PC was set to NULL
when we were trying to symbolize the stack. Unfortunately a UBSAN error,
triggered when we decremented the NULL pointer, masked the original problem in
this case. (was:
ClientFailoverOnNegotiationTimeoutITest.Kudu1580ConnectToTServer failed in ASAN
mode with what appeared to be a flake, but after more investigation (see
attached log file) there appears to be some case where the PC was set to NULL
when we were trying to symbolize the stack. Unfortunately a UBSAN error,
triggered when we decremented the NULL pointer, masked the original problem in
this case.)
> Possible stack-smashing bug
> ---------------------------
>
> Key: KUDU-2433
> URL: https://issues.apache.org/jira/browse/KUDU-2433
> Project: Kudu
> Issue Type: Bug
> Reporter: Mike Percy
> Priority: Major
> Attachments: client-negotiation-failover-itest.txt
>
>
> Edit: ClientFailoverOnNegotiationTimeoutITest.Kudu1580ConnectToTServer failed
> in ASAN mode with what appeared to be a flake, but after more investigation
> (see attached log file) there appears to be some case where the PC was set to
> NULL when we were trying to symbolize the stack. Unfortunately a UBSAN error,
> triggered when we decremented the NULL pointer, masked the original problem
> in this case.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
