[jira] [Commented] (TS-2564) Segmentation fault in 4.2.0-rc0

["William Bardwell (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13935949#comment-13935949 ] 

William Bardwell commented on TS-2564:
--------------------------------------

Could this be the same as TS-1547?
(If so you would be able to see  MIMEFieldBlockImpl::unmarshal() getting entries from cache where field->m_readiness != MIME_FIELD_SLOT_READINESS_LIVE (but where it has a pointer), which can cause problems later...maybe like that stack, although it is quite a bit different than the one in TS-1547)

> Segmentation fault in 4.2.0-rc0
> -------------------------------
>
>                 Key: TS-2564
>                 URL: https://issues.apache.org/jira/browse/TS-2564
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: HTTP
>            Reporter: Bryan Call
>            Assignee: Bryan Call
>            Priority: Blocker
>              Labels: crash
>             Fix For: 4.2.0
>
>
> Segmentation fault in mime_hdr_set_accelerators_and_presence_bits() in 4.2.0-rc0:
> {code}
> (gdb) bt
> #0  mime_hdr_set_accelerators_and_presence_bits (mh=0x2acd02e108c8, field=<value optimized out>, detach_all_dups=false) at MIME.cc:469
> #1  mime_hdr_field_detach (mh=0x2acd02e108c8, field=<value optimized out>, detach_all_dups=false) at MIME.cc:1538
> #2  0x00000000005c322c in mime_hdr_field_delete (heap=0x2acd02e10810, mh=0x2acd02e108c8, field=0x2acd02e10ab8, delete_all_dups=<value optimized out>) at MIME.cc:1586
> #3  0x000000000053cb5b in field_delete (cached_header=0x2acde002fa40, response_header=0x2accc168b1d8) at ../../proxy/hdrs/MIME.h:1107
> #4  field_delete (cached_header=0x2acde002fa40, response_header=0x2accc168b1d8) at ../../proxy/hdrs/MIME.h:1115
> #5  HttpTransact::merge_response_header_with_cached_header (cached_header=0x2acde002fa40, response_header=0x2accc168b1d8) at HttpTransact.cc:4914
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)