crash in RangeTransform::handle_event
-------------------------------------
Key: TS-1111
URL: https://issues.apache.org/jira/browse/TS-1111
Project: Traffic Server
Issue Type: Bug
Reporter: Zhao Yongming
Assignee: weijin
we have some crashing in range requesting processing, it is on our own tree
based on 3.0.x, that maybe the root cause of the do_io_close issue, we are
still look at how to fix that, feedback is welcome
{code}
#0 0x00000000004dc624 in RangeTransform::handle_event (this=0x2aaed0001fb0,
event=1, edata=<value optimized out>) at Transform.cc:926
926 Debug("transform_range", "RangeTransform destroy: %d",
m_output_vio ? m_output_vio->ndone : 0);
(gdb) bt
#0 0x00000000004dc624 in RangeTransform::handle_event (this=0x2aaed0001fb0,
event=1, edata=<value optimized out>) at Transform.cc:926
#1 0x000000000069145f in EThread::process_event (this=0x2aaaab332010,
e=0x591d410, calling_code=1) at I_Continuation.h:146
#2 0x0000000000691b8b in EThread::execute (this=0x2aaaab332010) at
UnixEThread.cc:218
#3 0x000000000069092e in spawn_thread_internal (a=0x440bfa0) at Thread.cc:88
#4 0x000000359fe0673d in pthread_create@@GLIBC_2.2.5 () from
/lib64/libpthread.so.0
#5 0x0000000000000000 in ?? ()
(gdb) p m_output_vio
$1 = (VIO *) 0x2aaed0029fe8
(gdb) p *m_output_vio
Cannot access memory at address 0x2aaed0029fe8
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
