You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Sudheer Vinukonda (JIRA)" <ji...@apache.org> on 2014/06/16 23:08:02 UTC
[jira] [Commented] (TS-2882) Core dump in handlEvent in handling
event VC_EVENT_INACTIVITY_TIMEOUT
[ https://issues.apache.org/jira/browse/TS-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14032952#comment-14032952 ]
Sudheer Vinukonda commented on TS-2882:
---------------------------------------
Adding some error checking and debug logs via TS-2883.We have had other changes (like turning off session reuse plugin for different reasons) on the hosts, so, not sure, if the fix really resolves this core. Nevertheless, since, I saw these error messages appear at the time of the core dump, would be good to have these included.
> Core dump in handlEvent in handling event VC_EVENT_INACTIVITY_TIMEOUT
> ---------------------------------------------------------------------
>
> Key: TS-2882
> URL: https://issues.apache.org/jira/browse/TS-2882
> Project: Traffic Server
> Issue Type: Bug
> Components: Core, SPDY
> Reporter: Sudheer Vinukonda
>
> {code}
> (gdb)
> #0 0x000000000070f3f7 in handleEvent (event=105, vc=0x2b5f1c27baf0) at ../../iocore/eventsystem/I_Continuation.h:146
> #1 read_signal_and_update (event=105, vc=0x2b5f1c27baf0) at UnixNetVConnection.cc:138
> #2 0x000000000071381f in UnixNetVConnection::mainEvent (this=0x2b5f1c27baf0, event=<value optimized out>, e=<value optimized out>) at UnixNetVConnection.cc:1066
> #3 0x00000000007080c5 in handleEvent (this=0x1bd9130, event=<value optimized out>, e=0x13888d0) at ../../iocore/eventsystem/I_Continuation.h:146
> #4 InactivityCop::check_inactivity (this=0x1bd9130, event=<value optimized out>, e=0x13888d0) at UnixNet.cc:80
> #5 0x000000000073409f in handleEvent (this=0x2b5ec2eb2010, e=0x13888d0, calling_code=2) at I_Continuation.h:146
> #6 EThread::process_event (this=0x2b5ec2eb2010, e=0x13888d0, calling_code=2) at UnixEThread.cc:145
> #7 0x0000000000734c13 in EThread::execute (this=0x2b5ec2eb2010) at UnixEThread.cc:224
> #8 0x000000000073344a in spawn_thread_internal (a=0x174b830) at Thread.cc:88
> #9 0x00002b5c8b3de851 in start_thread () from /lib64/libpthread.so.0
> #10 0x000000366a4e894d in clone () from /lib64/libc.so.6
> (gdb) frame 0
> #0 0x000000000070f3f7 in handleEvent (event=105, vc=0x2b5f1c27baf0) at ../../iocore/eventsystem/I_Continuation.h:146
> 146 return (this->*handler) (event, data);
> (gdb) print this
> $6 = (Continuation * const) 0x2b6196ab9f40
> (gdb) print *this
> $7 = {<force_VFPT_to_top> = {_vptr.force_VFPT_to_top = 0x15}, handler = &virtual table offset 20, this adjustment 1, mutex = {m_ptr = 0x6d2e35676d2d7375}, link = {<SLink<Continuation>> = {
> next = 0x6f6861792e6c6961}, prev = 0x6d6f632e6f}}
> (gdb) print this->handler
> $8 = &virtual table offset 20, this adjustment 1
> (gdb) print this->*handler
> Cannot access memory at address 0x1500000000000010
> (gdb) print event
> $9 = 105
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)