[
https://issues.apache.org/jira/browse/TS-4974?focusedWorklogId=30874&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-30874
]
ASF GitHub Bot logged work on TS-4974:
--------------------------------------
Author: ASF GitHub Bot
Created on: 19/Oct/16 14:20
Start Date: 19/Oct/16 14:20
Worklog Time Spent: 10m
Work Description: Github user SolidWallOfCode commented on the issue:
https://github.com/apache/trafficserver/pull/1113
Seems fine. The write on the server `netVC` points back at the `HttpSM` so
if that write fails this path would be followed with `data` being the write
`VIO`.
Issue Time Tracking
-------------------
Worklog Id: (was: 30874)
Time Spent: 40m (was: 0.5h)
> Bad debug assert in HttpSM::handle_server_setup_error
> -----------------------------------------------------
>
> Key: TS-4974
> URL: https://issues.apache.org/jira/browse/TS-4974
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Affects Versions: 7.0.0
> Reporter: Susan Hinrichs
> Assignee: Susan Hinrichs
> Fix For: 7.1.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When running with debug_enable, the non-release assert in
> HttpSM::handle_server_setup_error sometimes goes off.
> ink_assert(server_entry->read_vio == data);
> In the crash case, the data corresponds to server_entry->write_vio. Reviewing
> the function, I don't see why it is bad that this function is called with the
> write vio. The actual IO operations are performed against
> server_entry->read_vio and server_entry->write_io instead of the parameter
> vio directly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
